pr-description
Write a clear pull-request description that gets reviewed fast and merged with confidence. Use when opening a PR, summarizing a change for review, or asked to write a PR/merge-request description. Produces a structured PR: what changed and why, how it was tested, risk and rollout, and a focused reviewer guide — so the reviewer understands intent before reading a single diff line.
npx skills add mohitagw15856/pm-claude-skills --skill pr-description --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 Skill A good PR description is a gift to the reviewer: it explains *intent* before they read the diff, so review is fast and confident. This skill turns a change into a structured PR write-up — what and why, how it was tested, the risk, and where to focus — the difference between a one-pass approval and three rounds of confused back-and-forth. ## Required Inputs Ask for these only if they aren't already provided: - **The change** — what was done (the diff summary, commits, or a description). - **The why** — the problem/issue it solves (link the ticket). - **Testing** — how it was verified (tests added, manual steps, edge cases checked). - **Risk & rollout** — blast radius, migrations, flags, backward compatibility, how to roll back. ## Output Format ### [Concise, imperative PR title] (e.g. "Add rate limiting to the login endpoint") **What & why** — 2–4 sentences: the problem and what this change does about it. Link the issue (`Closes #123`). **Changes** — the key changes as bullets (the substantive ones, not every file). Group if large. **How it was tested** — tests added/updated, and the manual verification + edge cases checked. Be specific enough that the reviewe
- Required Inputs
- Output Format
- [Concise, imperative PR title] (e.g. "Add rate limiting to the login endpoint")
- Quality Checks
- Anti-Patterns
- Based On
What does the pr-description skill do?
Write a clear pull-request description that gets reviewed fast and merged with confidence. Use when opening a PR, summarizing a change for review, or asked to write a PR/merge-request description. Produces a structured PR: what changed and why, how it was tested, risk and rollout, and a focused reviewer guide — so the reviewer understands intent before reading a single diff line.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill pr-description --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.