Stats
Actions
Tags
From claude-code-toolkit
Generate structured pull request descriptions from diffs or branch changes. Produces a clear summary, change list, testing notes, and review guidance. Use when creating a PR or when asked to write a PR description.
How this skill is triggered — by the user, by Claude, or both
Slash command
/claude-code-toolkit:pr-descriptionThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Generate clear, structured pull request descriptions that help reviewers
Generate clear, structured pull request descriptions that help reviewers understand what changed, why, and how to verify it.
git diff main...HEAD (or the target branch)## Summary
[1-3 sentences: what this PR does and why. Should answer "what problem does
this solve?" without requiring the reviewer to read the diff.]
## Changes
[Grouped by area, not by file. Each item explains the *what* and *why*,
not just the file name.]
### [Area 1, e.g., "Authentication"]
- [Change description with motivation]
- [Change description with motivation]
### [Area 2, e.g., "API Layer"]
- [Change description with motivation]
## Testing
[How to verify this works. Be specific enough that someone unfamiliar with
the feature can test it.]
1. [Step 1]
2. [Step 2]
3. [Expected result]
## Screenshots / Recordings
[If UI changed, note that screenshots should be added. If no UI change,
say "N/A — no UI changes".]
## Notes for Reviewers
[Anything the reviewer should pay special attention to: tricky logic,
intentional deviations from patterns, known limitations, follow-up work.]
## Checklist
- [ ] Tests added/updated for changed logic
- [ ] Documentation updated (if public API changed)
- [ ] No secrets or credentials in the diff
- [ ] Breaking changes noted (if any)
- [ ] Tested locally before opening PR
Extend this checklist with project-specific items in your .github/PULL_REQUEST_TEMPLATE.md or .claude/rules/.
npx claudepluginhub rsurasin/claude-code-toolkit --plugin claude-code-toolkitGenerates structured PR descriptions from a git diff, commit list, or change summary. Covers what changed, why, and how to test.
Generates structured PR descriptions from git diffs with categorized changes, review checklists, risk assessments, and test summaries. Use for PR reviews and diff documentation.
Reads task files from tasks/<branch>/ and the diff against the detected base ref, then generates a polished PR description in markdown for the user to copy-paste.