pr-description-live
Write a PR description grounded in the REAL diff — read the branch's actual changes via the GitHub connector, not a template the user fills in. Use when asked to write my PR description, describe this pull request, draft the PR body from my branch, or document these changes in Cowork. Reads the commits and diff via the GitHub connector, derives what changed and why from the code itself, and produces a PR-description artifact (summary, changes, testing, risk) ready to paste — matching the repo's PR template if one exists.
npx skills add mohitagw15856/pm-claude-skills --skill pr-description-live --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 (Live) A good PR description is written *from the diff*, not from memory — memory forgets the file you touched at 2am. In Claude Cowork this skill reads the *actual* changes on the branch and writes the description grounded in them, so the reviewer gets an accurate map of what moved and why. ## What This Skill Produces - **The PR description** — summary, the changes grouped by area, how it was tested, and the risk/rollout — all derived from the real diff - **Template-matched output** — if the repo has a PR template, the body fills its sections; otherwise a clean default - **The reviewer's map** — the one or two files/decisions that deserve the closest look ## Required Inputs Ask for these if not provided: - **The branch/PR** — the branch name or PR number, and the base it targets - **The why** — the issue/ticket or one line of intent (the diff shows *what*, not always *why*) - **Audience** — internal team vs open-source contributors — tone and detail follow ## Framework: A Description a Reviewer Trusts 1. **Summary** — what this PR does and why, in two or three lines. 2. **Changes, grouped** — by area/feature, not a raw file list; each with its purpose. 3. **Testin
- What This Skill Produces
- Required Inputs
- Framework: A Description a Reviewer Trusts
- Execution (Cowork)
- Output Format
- Summary
- Changes
- Testing
- Risk & rollout
- Look here first
- Quality Checks
- Anti-Patterns
- Example Trigger Phrases
What does the pr-description-live skill do?
Write a PR description grounded in the REAL diff — read the branch's actual changes via the GitHub connector, not a template the user fills in. Use when asked to write my PR description, describe this pull request, draft the PR body from my branch, or document these changes in Cowork. Reads the commits and diff via the GitHub connector, derives what changed and why from the code itself, and produces a PR-description artifact (summary, changes, testing, risk) ready to paste — matching the repo's PR template if one exists.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill pr-description-live --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.