gh-prs
Installation
SKILL.md
Pull requests
A pull request is where a change earns its way into the default branch. A good PR is small enough to review, titled so its history reads cleanly, described so a reviewer knows why without reading every line, and honest about what's been verified. This standard applies to every PR you open, review, or merge — it isn't a step you wait to be asked for.
Before you open
Run these checks before every gh pr create, in order:
- Is there already an open PR for this? Run
gh pr listand look for one covering the same page, section, or component and the same kind of change (feat,fix,ci…). If there is, push to that PR's branch and update its body and test plan — don't open a new one. Never stack a PR on top of another open PR. On a squash-merge repo, squashing the bottom PR forces a rebase of everything above it, and every rebase reruns all its CI. - Is there an issue? Every PR has a linked issue, however small the change — a two-line CSS fix included. It's for traceability, not ceremony. If none exists, file one first from
.github/ISSUE_TEMPLATE/with aDone whenchecklist (see thegh-issuesskill). When a follow-up lands on an existing PR and gets its own issue, add a secondCloses #Nline to that PR's body. - Will it conflict with other open PRs? Before branching, check that the new work stays clear of lines other open PRs touch:
git merge-tree --write-tree <your-branch> <their-branch>exits non-zero and lists the files when they'd conflict. Keep your edits away from those lines where you can. - Never work on
main. Branch off an up-to-datemain; never push directly to it.
Open as a draft while it's in progress, and mark it ready only when the test plan can actually pass. Don't request review on something you know is red.
Size — group related work, keep it small
Small means one logical change, not one tiny edit. Every merge costs a full CI run, so a swarm of one-line PRs burns Actions minutes; one sprawling PR is unreviewable. Between the two: