pr-description-writer
Write a clear, structured pull request description from a git diff, branch summary, or commit list. Use when asked to write a PR description, draft a pull request, or document code changes. Produces a description with summary, motivation, changes made, testing steps, and reviewer guidance.
npx skills add mohitagw15856/pm-claude-skills --skill pr-description-writer --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# PR Description Writer Skill Writes structured, reviewer-friendly pull request descriptions from a diff, commit list, or informal notes. Covers the what, why, and how-to-review so reviewers can start immediately. ## Required Inputs Ask for these if not provided: - **What changed** (paste a git diff, `git log --oneline`, or describe the changes in plain English) - **Why it was changed** (the problem being solved or feature being added) - **How to test it** (any specific steps a reviewer needs to verify it works) - **Risk level** (low / medium / high — affects how much reviewer guidance to include) - **PR type** (feature / bug fix / refactor / dependency upgrade / config change / hotfix) - **Target branch** (e.g. main / develop / release/2.4 — affects risk framing and reviewer guidance) - **Linked issue or ticket** (e.g. JIRA-1234, GitHub #567 — or "none") ## Output Format ### Title A clear, imperative-mood title under 72 characters: `[type]: [concise description of what changed]` Examples: - `feat: add rate limiting to the public API` - `fix: resolve race condition in session expiry` - `refactor: extract payment logic into PaymentService` ### Summary 2–3 sentences covering: - What
- Required Inputs
- Output Format
- Title
- Summary
- Changes Made
- Screenshots / Demo
- How to Test
- Testing Checklist
- Reviewer Notes
- Related
- Deeper Materials
- Scoring Rubric (0–40)
- Quality Checks
- Anti-Patterns
What does the pr-description-writer skill do?
Write a clear, structured pull request description from a git diff, branch summary, or commit list. Use when asked to write a PR description, draft a pull request, or document code changes. Produces a description with summary, motivation, changes made, testing steps, and reviewer guidance.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill pr-description-writer --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.