Use when opening or updating a GitHub PR - writes a detailed PR description that explains what changed, why it changed, how it was implemented, and how it was tested.
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
# PR Description Writer
Create and publish high-quality PR descriptions that help reviewers understand intent, implementation details, and verification steps.
## When to Use
- Opening a new PR
- Refreshing a stale or minimal PR description
- Capturing implementation rationale for future debugging
## Goals
Every PR body should clearly answer:
1. What changed?
2. Why did we make this change now?
3. How was it implemented?
4. How was it tested?
5. What risks or follow-ups remain?
## Workflow
1. Discover PR context and changed files.
2. Extract intent from commit(s) and code changes.
3. Draft a structured PR body.
4. Apply the body to the PR.
5. Re-open the PR view and confirm body/labels.
## Commands
```bash
# Identify the active PR for current branch
gh pr view --json number,title,url,baseRefName,headRefName
# Inspect changed files and patch summary
gh pr diff --name-only
gh pr diff
# Review commit messages for intent
git log --oneline --decorate -n 10
# Apply updated body
gh pr edit <pr-number> --body-file /tmp/pr-body.md
```
## Body Structure
Use the template in [references/pr-body-template.md](references/pr-body-template.md).
Required sections:
- `## Why`
…
The line at the top of this page pins the label git:20260718.85ce762, 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_sf7uta3srtqgshgh
GET https://markdownregistry.com/api/v1/resolve?ref=basicmachines-co/basic-memory/pr-description
GET https://markdownregistry.com/api/v1/blob/26554a60eea5de496124da3dff94d270b7032afb3ec9dc6f6b089b6398ca04b2
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.
basicmachines-co/basic-memory · .agents/skills/adversarial-review/SKILL.md · Cross-vendor adversarial code review of the current branch. Two different model families (Claude + Codex/GPT) review…
basicmachines-co/basic-memory · .agents/skills/cmux-markdown/SKILL.md · Open markdown files in a formatted viewer panel with live reload. Use when you need to display plans, documentation, or…
basicmachines-co/basic-memory · .agents/skills/cmux-settings/SKILL.md · View and edit cmux settings in ~/.config/cmux/cmux.json. Use when the user wants to change cmux preferences…
basicmachines-co/basic-memory · .agents/skills/cmux-workspace/SKILL.md · Work inside the current cmux workspace and terminal. Use for cmux workspace, current workspace, caller surface, panes…
basicmachines-co/basic-memory · .agents/skills/code-review/SKILL.md · Use when reviewing Basic Machines code for house style, architecture risk, pre-merge hardening, or whether a change…
basicmachines-co/basic-memory · .agents/skills/infographics/SKILL.md · Use when generating Basic Memory PR, changelog, release, or weekly images from Codex.
basicmachines-co/basic-memory · .agents/skills/instrumentation/SKILL.md · Add Pydantic Logfire observability to applications. Use this skill whenever the user asks to "add logfire", "instrument…
basicmachines-co/basic-memory · .agents/skills/pr-create/SKILL.md · Use when explicitly creating or updating a Basic Memory pull request. This compatibility entry point delegates the full…
basicmachines-co/basic-memory · .agents/skills/pr-review-loop/SKILL.md · Enforce the Basic Machines GitHub PR review loop before merging. Use whenever Codex is preparing to merge…
basicmachines-co/basic-memory · .agents/skills/pull-request/SKILL.md · Drive GitHub pull request work end to end. Use when Codex is asked to open, update, describe, push to, monitor, review…
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…
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…
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…
