Generate a clear, reviewer-friendly pull-request description from a diff, covering what changed, why, risk, and how it was tested. Use when opening a pull request or writing/improving a PR body.
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
Write a pull-request description from the actual changes on this branch. Base it on the diff, not on what you assume was intended.
## Gather context
- Diff the branch against its base (default to the repo's main branch, or the base the user named): review the changed files, the commits, and their messages.
- Identify the linked issue/ticket if one is referenced in the branch name, commits, or arguments.
- Separate the substantive change from incidental churn (formatting, renames, generated files).
## Write the description
Use this structure, omitting any section that genuinely doesn't apply:
- **Summary**: one or two sentences on what this PR does.
- **What changed**: the concrete changes, grouped logically, referencing key files.
- **Why**: the motivation or problem being solved; link the issue.
- **Risk / impact**: blast radius, backward compatibility, breaking changes, data migrations, config/env or infra changes, anything reviewers should scrutinise.
- **Testing**: how it was verified, including tests added/updated, manual steps, and explicitly what was *not* covered.
- **Notes for reviewers**: trade-offs, follow-ups, screenshots for UI changes.
## Rules
…
The line at the top of this page pins the label git:20260921.b1a4652, 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_iqokvwu7hyyk5zle
GET https://markdownregistry.com/api/v1/resolve?ref=khaledsaeed18/dotclaude/pr-description
GET https://markdownregistry.com/api/v1/blob/cd2d8d33baa451e50b47c192480b24b05c7b5ec4bcb5198a49d5273487ea505f
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.
khaledsaeed18/dotclaude · .agents/skills/improve/SKILL.md · Survey any codebase as a senior advisor and produce prioritized, self-contained implementation plans for OTHER…
khaledsaeed18/dotclaude · .claude-plugin/plugins/deploy/skills/coolify-image-app/SKILL.md · Create and configure a Coolify application that runs a prebuilt image from a registry. Use when adding an app to…
khaledsaeed18/dotclaude · .claude-plugin/plugins/deploy/skills/coolify-vps-baseline/SKILL.md · Prepare a Linux VPS to run production containers under Coolify. Use when setting up a new server, auditing an existing…
khaledsaeed18/dotclaude · .claude-plugin/plugins/deploy/skills/deploy-verification/SKILL.md · Prove a deployment from the server side. Use when a deploy finished and needs sign-off, when a rolling update may have…
khaledsaeed18/dotclaude · .claude-plugin/plugins/deploy/skills/express-prisma-coolify-image/SKILL.md · Package an Express and Prisma API as a runtime-only image that migrates its Postgres database at start. Use when…
khaledsaeed18/dotclaude · .claude-plugin/plugins/deploy/skills/ghcr-coolify-pipeline/SKILL.md · Write the single GitHub Actions workflow that takes a repository from pull request to production through GHCR and…
khaledsaeed18/dotclaude · .claude-plugin/plugins/deploy/skills/live-domain-cutover/SKILL.md · Move a live domain from one host to another without downtime or lost sessions, with a rehearsal, a timed DNS switch, a…
khaledsaeed18/dotclaude · .claude-plugin/plugins/deploy/skills/nextjs-coolify-image/SKILL.md · Package a Next.js app as a runtime-only container image with a health probe and a fast shutdown. Use when…
khaledsaeed18/dotclaude · .claude-plugin/plugins/deploy/skills/proxy-client-address/SKILL.md · Forward the real client address from a server-side proxy to a backend without trusting forgeable headers. Use when an…
khaledsaeed18/dotclaude · .claude-plugin/plugins/deploy/skills/vps-ops-toolkit/SKILL.md · Install host operations on a VPS, with a cron health check that alerts on change, restore-verified encrypted database…
khaledsaeed18/dotclaude · .claude-plugin/plugins/docs/skills/adr-writing/SKILL.md · Write Architecture Decision Records that a future engineer can act on: a numbered, immutable record with the context…
khaledsaeed18/dotclaude · .claude-plugin/plugins/docs/skills/openapi-spec/SKILL.md · Write, generate, or review an OpenAPI 3.1 specification for an HTTP API so that it is accurate to the implementation…
untrivial-ai/agent-orchestrator · .agents/skills/pr-description/SKILL.md · Write and maintain pull request descriptions in this repository, including the required change-count header, the…
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…
qa-aman/claude-skills · skills/by-role/engineer/pr-description/SKILL.md · Write a clear pull request description. Use when the user says "write a PR description", "PR template", "pull request…