pr-description is agent-read markdown (skill) from khaledsaeed18/dotclaude: 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..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns 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
…
Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
GET https://markdownregistry.com/api/v1/artifacts/art_xdmu46m6yigj3aql
GET https://markdownregistry.com/api/v1/resolve?ref=khaledsaeed18/dotclaude/pr-description
GET https://markdownregistry.com/api/v1/blob/a1194e89f9f950d2d607f8ebb36231587cb4be38e7896c9cd71b667d34bfd4f9
Your agent 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/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…
khaledsaeed18/dotclaude · .claude-plugin/plugins/docs/skills/readme-writing/SKILL.md · Write or restructure a README that gets a reader from landing to first success in minutes: a one-line purpose, a…
khaledsaeed18/dotclaude · .claude-plugin/plugins/docs/skills/technical-writing/SKILL.md · Write and edit developer documentation, guides, design notes, and engineering blog posts with a working writer's…
khaledsaeed18/dotclaude · .claude-plugin/plugins/engineering/skills/adversarial-reviewer/SKILL.md · Review code through three hostile personas - the Saboteur, the New Hire, and the Security Auditor - each required to…
khaledsaeed18/dotclaude · .claude-plugin/plugins/engineering/skills/api-design-review/SKILL.md · Review an API contract (REST or GraphQL) before or while it is implemented, checking resource naming, HTTP semantics…
khaledsaeed18/dotclaude · .claude-plugin/plugins/engineering/skills/code-review-response/SKILL.md · Process code-review feedback with technical rigour. Understand each point, check it against the actual codebase, and…
khaledsaeed18/dotclaude · .claude-plugin/plugins/engineering/skills/db-migration-safety/SKILL.md · Review or write a database schema migration with production safety as the bar, checking locks, table rewrites…
khaledsaeed18/dotclaude · .claude-plugin/plugins/engineering/skills/dependency-upgrade/SKILL.md · Upgrade dependencies without breaking the project: audit what is outdated and why it matters (security, EOL, features)…
khaledsaeed18/dotclaude · .claude-plugin/plugins/engineering/skills/dockerfile-best-practices/SKILL.md · Write or review a Dockerfile and compose setup for a production service: multi-stage builds that ship only the runtime…
khaledsaeed18/dotclaude · .claude-plugin/plugins/engineering/skills/error-handling-patterns/SKILL.md · Design and review error handling in a codebase: which errors are expected results versus bugs, typed error hierarchies…
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…
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…
