Write a clear pull request description. Use when the user says "write a PR description", "PR template", "pull request description", "how do I describe this change", "commit message for this", "document this change", "open a PR for", or is about to merge code and needs to communicate what changed and why - even if they don't explicitly say "PR description".
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
## Overview
Based on **"The Pragmatic Programmer"** by Hunt & Thomas. Hunt & Thomas: "It's not just code you're writing - it's communication." A PR description is a letter to your reviewers (and to your future self). It should answer: what changed, why it changed, how to verify it, and what to watch out for. A reviewer who has to read all the code to understand the PR is doing your job for you.
## Workflow
### Step 1: Write the title
Format: `[type]: [short description in imperative mood]`
Types: `feat`, `fix`, `refactor`, `test`, `chore`, `docs`
Rules:
- Imperative mood: "add pagination" not "added pagination" or "adds pagination"
- Under 72 characters
- Specific: "fix null pointer in payment processing" not "fix bug"
### Step 2: Write the Summary
2-4 sentences. Answer: what does this PR do?
Write for someone who hasn't seen the issue, ticket, or conversation. They should understand the change from this paragraph alone.
### Step 3: Write the Motivation (Why)
Why was this change needed? Link the ticket but don't rely on the link - links rot.
If it's a bug fix: what was broken and what impact did it have?
If it's a feature: what user need or business goal does it serve?
…
The line at the top of this page pins the label git:20260303.09b1726, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_ggtobv6d26pscnql
GET https://markdownregistry.com/api/v1/resolve?ref=qa-aman/claude-skills/pr-description
GET https://markdownregistry.com/api/v1/blob/58f983f2b25179fd7ed7db21d756033568080711ed2c3e5f7fada159fe37ce77
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
qa-aman/claude-skills · .claude/skills/create-skill/SKILL.md · Create or update Claude Code skills following Anthropic's official skill standard. Use when user says "create a skill"…
qa-aman/claude-skills · .claude/skills/sync-skills/SKILL.md · Fetch skills from projects on the current system, genericize them, and add to the claude-skills repository. Use when…
qa-aman/claude-skills · skills/by-role/accountant/audit-workpaper/SKILL.md · Write a clear, reviewable audit workpaper documenting procedures, evidence, and conclusions. Use when an auditor says…
qa-aman/claude-skills · skills/by-role/accountant/budget-variance-analysis/SKILL.md · Analyze budget vs. actual variances, identify root causes, and recommend corrective actions. Use when an accountant or…
qa-aman/claude-skills · skills/by-role/accountant/financial-statement-review/SKILL.md · Analyze and interpret financial statements to surface performance signals, quality concerns, and red flags. Use when an…
qa-aman/claude-skills · skills/by-role/accountant/month-end-close/SKILL.md · Run, document, or review a structured month-end close process. Use when an accountant says "help me with month-end…
qa-aman/claude-skills · skills/by-role/accountant/tax-position-memo/SKILL.md · Write a technical tax position memo that documents a tax filing position with authorities, facts, analysis, and…
qa-aman/claude-skills · skills/by-role/business-analyst/acceptance-criteria-writer/SKILL.md · Write measurable acceptance criteria for requirements or user stories. Use when the user says "write acceptance…
qa-aman/claude-skills · skills/by-role/business-analyst/brd-writer/SKILL.md · Write a Business Requirements Document. Use when the user says "write a BRD", "business requirements", "document the…
qa-aman/claude-skills · skills/by-role/business-analyst/cost-benefit-analysis/SKILL.md · Build a business case with costs, benefits, and ROI. Use when the user says "cost-benefit analysis", "business case"…
qa-aman/claude-skills · skills/by-role/business-analyst/data-dictionary/SKILL.md · Generate a data dictionary documenting entities, fields, and business rules. Use when the user says "data dictionary"…
untrivial-ai/agent-orchestrator · .agents/skills/pr-description/SKILL.md · Calculate and maintain the required change-count header when creating or updating pull requests in this repository.
basicmachines-co/basic-memory · .agents/skills/pr-description/SKILL.md · Use when opening or updating a GitHub PR - writes a detailed PR description that explains what changed, why it changed…
tanstack/ai · .claude/skills/pr-description/SKILL.md · Use when writing a pull request title or body, when about to run gh pr create, when about to git push on a branch that…
tanstack/ai · .grok/skills/pr-description/SKILL.md · Use when writing a pull request title or body, when about to run gh pr create, when about to git push on a branch that…
tanstack/ai · .agents/skills/pr-description/SKILL.md · Use when writing a pull request title or body, when about to run gh pr create, when about to git push on a branch that…
zhuyansen/agent-skills-hub · ops/skillmgr-runs/in/input/library/pr-description/SKILL.md · Write a pull request description from the diff: what changed, why, and how it was tested.
justxor/claude-code-pro-course · starter-kit/.claude/skills/pr-description/SKILL.md · Готовит заголовок и описание pull request по изменениям в ветке. Используй, когда просят описать PR, подготовить pull…
khaledsaeed18/dotclaude · .claude-plugin/plugins/git/skills/pr-description/SKILL.md · Generate a clear, reviewer-friendly pull-request description from a diff, covering what changed, why, risk, and how it…