What do I need to use PR Description Writer?

What changed; Why it was changed; How to test it; Risk level; PR type; Target branch; Linked issue or ticket.

Is PR Description Writer free to use?

Yes — run it free in the browser playground (no API key needed for the sponsored trial, or bring any provider key), or install it into Claude Code, Cursor, ChatGPT and more via npx pm-claude-skills. MIT-licensed and open source.

PR Description Writer

Q: How do I know the PR Description Writer output is good?

The skill verifies itself against its own quality checks: Title is imperative mood and under 72 characters; Summary explains what AND why (not just what); Changes list describes logical changes (not file-by-file changes); Title starts with a valid type prefix (feat / fix / refactor / chore / deps / config / hotfix) and is under 72 characters.

🟢 Production-Ready🕐 updated 2026-07-14 🔷 SkillSpec L3 pm-engineering

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.

▶ Run it free — no key needed 📝 Grade your existing draft View SKILL.md ↗

What to give it

▸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"

✅ The bar it holds itself to

Every skill in this library self-verifies — these are this skill's own quality checks, straight from its definition.

✓Title is imperative mood and under 72 characters

✓Summary explains what AND why (not just what)

✓Changes list describes logical changes (not file-by-file changes)

✓Title starts with a valid type prefix (feat / fix / refactor / chore / deps / config / hotfix) and is under 72 characters

✓Testing steps are reproducible by someone unfamiliar with the code

✓For high-risk PRs, Reviewer Notes flags at least one specific area of concern or deliberate trade-off; for low-risk PRs, Reviewer Notes is either omitted or kept to one line

⚠️ What it refuses to do

Do not write a description that only restates what changed — explain why the change was made

Do not skip the testing steps — reviewers need to know how to verify the change works

Do not omit the reviewer notes for high-risk PRs — flag deliberate trade-offs and areas needing careful review

Do not describe implementation details that are obvious from the diff — add context that the diff cannot convey

Do not produce a single paragraph — structure with headers so reviewers can navigate to what they need

Install

npx pm-claude-skills add --agent claude   # or codex · cursor · gemini · hermes
# or one-line MCP (every skill, any client):
claude mcp add pm-skills -- npx -y pm-claude-skills-mcp

Start with

Related skills

🔌 Embed this skill

Drop this on your blog, docs, or site — it renders a "Run this skill" card:

<div data-pm-skill="pr-description-writer"></div>
<script src="https://mohitagw15856.github.io/pm-claude-skills/embed.js" async></script>

💬 Discussion

PR Description Writer is one of 1098 open-source professional AI agent skills — all SkillSpec L3. Try them all in the browser · ⭐ Star on GitHub · Browse the full catalog