Write and maintain pull request descriptions in this repository, including the required change-count header, the before-and-after section, and screenshots or recordings for visible changes.
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
Use the section order in `.github/pull_request_template.md`: change-count header,
What, Why, Before / After, How, Testing, Checklist. Preserve the rest of an existing
PR description when updating it.
## Change-count header
Begin every PR description with these three lines, using Markdown hard line breaks
so each renders separately:
```text
Code changes: +<added> -<deleted>
Tests: +<added> -<deleted>
Others: +<added> -<deleted>
```
Calculate the numbers from the net diff against the PR's actual base. For a local
branch, use `git diff --numstat <base>...<head>`. After pushing, prefer GitHub's
per-file additions and deletions. Recalculate after the final push rather than
summing commit churn or estimating counts.
Count every changed file exactly once:
- **Code changes:** handwritten implementation, including SQL, migrations, styles,
and executable scripts.
- **Tests:** test code, fixtures, snapshots, and test-only helpers.
- **Others:** generated or vendored files, lockfiles, documentation, configuration,
and assets. Generated output belongs here even when it contains source code.
…
The line at the top of this page pins the label git:20261027.bb870bd, 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_d7s2feduasnutrsd
GET https://markdownregistry.com/api/v1/resolve?ref=untrivial-ai/agent-orchestrator/pr-description
GET https://markdownregistry.com/api/v1/blob/1a1dd53304998aff28054e211d322369e8a636709cad03298ea5bd3d77ebfc70
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.
untrivial-ai/agent-orchestrator · .agents/skills/ao-desktop-dev/SKILL.md · Launch, restart, or troubleshoot the real AO Electron desktop app from this repository; run a checkout against isolated…
untrivial-ai/agent-orchestrator · .agents/skills/bug-triage/SKILL.md · Help clarify human bug reports, search for duplicates, and gather diagnostic evidence separately from a concise issue…
untrivial-ai/agent-orchestrator · .claude/skills/ao-desktop-dev/SKILL.md · Launch, restart, or troubleshoot the real AO Electron desktop app from this repository; run a checkout against isolated…
untrivial-ai/agent-orchestrator · .claude/skills/bug-triage/SKILL.md · Help clarify human bug reports, search for duplicates, and gather diagnostic evidence separately from a concise issue…
untrivial-ai/agent-orchestrator · DESIGN.md · Use for any renderer UI, visual polish, component, layout, theme, motion, or interaction change in Agent Orchestrator…
untrivial-ai/agent-orchestrator · backend/internal/skillassets/using-ao/SKILL.md · Catalog of the AO (Agent Orchestrator) `ao` CLI: spawning workers, managing sessions and projects, creating reusable…
untrivial-ai/agent-orchestrator · integrations/grok-bot/skills/ao-actions/SKILL.md · Direct actions on one AO session or PR: stop or interrupt, resume, merge a PR, start a review, screenshot a session's…
untrivial-ai/agent-orchestrator · integrations/grok-bot/skills/ao-answer/SKILL.md · Find AO sessions that wait on the user, show each question or approval as tap-to-answer options, and send the answer…
untrivial-ai/agent-orchestrator · integrations/grok-bot/skills/ao-orchestrator/SKILL.md · Talk to a project's AO orchestrator: pass the user's request to it, wait for its reply and relay it. The default route…
untrivial-ai/agent-orchestrator · integrations/grok-bot/skills/ao-rules/SKILL.md · Shared rules and the connection helper for every ao-* skill (run Orchestrator from chat). Read before running any ao-*…
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…
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…
