Gh pr
(1) Rigorous notes and solutions for core algorithms and computing fundamentals broken down for deliberate practice with Anki. (2) A monorepo of libraries and CLI tools I use regularly as a software engineer.
npx -y skills add Unique-Divine/jiyuu --skill gh-prAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Writes clear pull request descriptions from the current branch diff against a base branch. Defaults to `main`, but supports `dev` or any other user-specified comparison branch. Use when the user asks for a PR description, pull request summary, or a markdown write-up for changes against a base branch.
SKILL.md
1.8 KB, as published. Nobody here has run it
GH PR
Purpose
Create a clear, logical, and concise pull request description for the current branch diff against a base branch.
Instructions
When using this skill:
- Determine the comparison branch first:
- Use the branch the user specifies when they name one.
- Otherwise, default to
main. - If the correct base branch is unclear, ask the user before drafting the pull request description.
- If the repo clearly uses another default integration branch, such as
dev, use that instead of assumingmain.
- Write a pull request description that explains the rationale behind the changes, not just the file-by-file edits.
- Keep the writing concise and non-repetitive.
- Save the final output to a markdown file named
gh-pr.md.
Output format
Use this structure:
# <Short PR title>
<One short synopsis paragraph explaining the change and why it exists.>
- Closes <gh-issue-link> (If applicable, not all PRs pertain to issues)
## Key Changes
1. <Important change with rationale>
1. <Important change with rationale>
## Appendix
<Optional extra context, notes, follow-ups, or test details. Omit this section
if it does not add value.>
Style
- Prefer clarity over cleverness.
- Do not repeat the same point in multiple sections.
- Explain rationale wherever it is useful.
- Use numbered lists for the
## Key Changessection, writing each item with1.so the markdown source is easy to reorder. - Keep the description easy to scan.