pr-gen
Installation
SKILL.md
pr-gen
Generate or update a GitHub PR title and description from the final state of
the current branch (git diff "$base"...HEAD), not from commit history.
Principles
- Document
HEAD, not history. If a change was added then removed, it does not exist — do not mention it. - Verify before citing. Run
git show HEAD:<path> | grep …for every feature, file, symbol, or test you plan to reference. - Be concise. 15–30 lines is typical; ≤ 50 for genuinely complex PRs.
- Respect project conventions. If
.github/PULL_REQUEST_TEMPLATE.mdorCONTRIBUTING.mdexist, follow them exactly — they win over this skill's templates. - Refuse rather than fabricate. If the branch cannot satisfy the chosen
template's required sections, stop and tell the user what is missing. Do not
silently downgrade to a looser template, and never list a file, symbol, or
test that is not in
HEAD.