A Claude Code skill that turns your git diff into a clean, professional pull request description. Senior-engineer voice without the senior-engineer typing.
- Auto-detected issue refs (
Closes #123, JIRA, Linear) pulled from commit messages - Auto-flagged risk when the diff touches migrations, auth, deploy config, secrets, or public API surface
- Template-aware (feature / bugfix / refactor / hotfix / experiment) — tone + structure adapt to the type
- Honest Testing section with explicit "what's NOT tested" so reviewers don't have to ask
- Skim-able structure that leads with summary, lists files only when it matters, skips trivia
git clone https://github.com/matthewkim323/prwrite ~/.claude/skills/prwriteprwrite # full PR body from git diff <base>..HEAD
prwrite --template feature # explicit template
prwrite --staged # use staged changes (pre-commit mode)
prwrite --since HEAD~3 # last 3 commits
prwrite --copy # copy result to macOS clipboard
prwrite --ship # actually open the PR via gh CLI
prwrite --ship --draft # draft PR
prwrite --context kalilabs # load research/kalilabs/CONTEXT.md to match company voice
Or just say "write a pr description" / "draft a pr" / "pr body".
prwrite --ship
generates the description, runs gh pr create --body-file ..., prints the PR URL. zero copy-paste.
Output always includes (unless template skips one):
- Summary — 2-4 sentences anyone can read
- Problem — specific, with issue refs if found
- Solution — walks through key decisions
- Changes — file-level breakdown, grouped
- Testing — what you actually ran, what you didn't
- Risk & Rollback — auto-augmented based on what the diff touches
- Screenshots / Output — for UI or observable behavior
- Out of scope — what you intentionally didn't change
- Follow-up — what should happen post-merge
MIT.