Use when the user asks to write, draft, generate, or update a GitHub pull request description for the current branch. Reads the branch diff and commit messages, writes a structured PR body (summary, changes, testing), and optionally creates or updates the PR via the gh CLI.
SkillScore60Maintained
Automatic
◆Coding pack
Last verified 8/18/2026
What it changes
Passed 11 of 18 test cases with the skill, and 10 of 18 without it.
Without skill56%
With skill60%
Checks it passed that the model alone missed
References references/pr-format-guide.md
Omits the section entirely rather than outputting N/A
Verifies the summary uses active voice without filler phrases
and 2 more in the full report
5 fixed10 passed either way6 still failing4 broke
Pass-rate lift
+4 pp
Tokens
+7%
Agent turns
0%
Response time
-66%
Model gemini-3.6-flashMeasured 8/18/2026v115 of 25 cases passed with skill · 18 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 5
Prompt
Which reference file specifies the required section order and testing format before generating descriptions?
What was checked, without and with the skill
Checked
Without skill
With skill
References references/pr-format-guide.md
Missed
Passed
case-24 · gemini-3.6-flash · 8/18/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md129 lines2 files
PR Description Writer
Read the current branch diff and write a complete GitHub pull request description. Create or update the PR with one command.
Writing Style
Apply to all generated PR descriptions:
Active voice. "Adds X" not "X has been added."
Present tense for summary ("Adds caching layer"), past tense for context ("The old approach caused N requests per render")
Short sentences, one idea per bullet
No em dashes — use a comma or period instead
No filler: "this PR", "this commit", "as per the discussion"
Specifics beat generalities: "reduces p95 latency from 800ms to 90ms" beats "improves performance"
Step 1: Check Setup
Confirm gh is authenticated:
gh auth status
If not authenticated: gh auth login and follow the prompts.
Confirm the current directory is a git repo with an active branch:
git branch --show-current
If detached HEAD or no branch, stop and ask the user which branch they want to describe.