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
Run the checker. Do not reason about section names or ticket-ref wording:
```text
python <this-skill>/scripts/check_pr_body.py BODY.md
```
Fix whatever the script prints. The body is not ready until exit 0.
Use this template for writing the PR body:
```markdown
Refs #N
## Plan
<what will change and how we will know>
## Summary
<diagram, diff-sketch, or tree>
## Evidence
- **Before:** `VERIFY_FAIL` output from verify-loop
**After:** `VERIFY_PASS` output from verify-loop
## Merge Danger
**Door:** <one-way or two-way>
<optional: description>
**Blast Radius:** <one-word description>
<optional: potential ramifications of merge>
```
## Sections
Skip all preambles and keep prose brief. Use the user's domain language from `GLOSSARY.md`. Ticket links are `Refs #N` only.
### Plan
Short enough that `scripts/check_pr_body.py` sees a non-empty `## Plan` section: the change, the verify-loop command, and the door type.
### Summary
Pick the smallest view that makes the key point clear.
- Show logic or an algorithm as pseudocode:
```text
on(save)
if content is unchanged
return cached result
write new content
return fresh result
```
…
The line at the top of this page pins the label git:20261006.876cce4, 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_uxp7d24wasnq2xwg
GET https://markdownregistry.com/api/v1/resolve?ref=kunanonj/ai-skills-hub/pr
GET https://markdownregistry.com/api/v1/blob/b7ccf81d55b60e57b576231a6ca84d4620a78665e95dfd86dfbf5bef35d48929
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.
kunanonj/ai-skills-hub · plugins/superstacks/skills/code-review/SKILL.md · Use when reviewing a branch, PR, or WIP since a commit, tag, or merge-base. Two-axis Standards and Spec review via…
kunanonj/ai-skills-hub · plugins/superstacks/skills/diagnosing-bugs/SKILL.md · Use when the user says diagnose or debug this, or reports something broken, throwing, failing, or slow.
kunanonj/ai-skills-hub · plugins/superstacks/skills/domain-modeling/SKILL.md · Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
kunanonj/ai-skills-hub · plugins/superstacks/skills/gardening/SKILL.md · Use when finding small maintenance work. One concern per PR, each with a verify command and a small diff budget.
kunanonj/ai-skills-hub · plugins/superstacks/skills/grill-with-docs/SKILL.md · Use when grilling a plan or design that should also produce ADRs and a glossary as you go.
kunanonj/ai-skills-hub · plugins/superstacks/skills/grilling/SKILL.md · Use when the user wants to stress-test a plan, decision, or idea, or uses any grill trigger phrases.
kunanonj/ai-skills-hub · plugins/superstacks/skills/how/SKILL.md · Use for how-does-X-work walkthroughs, placement, ownership, and layering questions before changing code.
kunanonj/ai-skills-hub · plugins/superstacks/skills/intake-triage/SKILL.md · Use when a coordinator has a batch of bug reports, feedback, or alerts. Deduplicate, group, score two-way vs one-way…
kunanonj/ai-skills-hub · plugins/superstacks/skills/interrogate/SKILL.md · Use for interrogate, adversarial review, multi-model review, challenge this, stress test this code, or find blind spots.
kunanonj/ai-skills-hub · plugins/superstacks/skills/mistake-to-constraint/SKILL.md · Use when a mistake repeats. Encode it as the strongest guard — type or runtime, lint, test, directory convention, then…
kunanonj/ai-skills-hub · plugins/superstacks/skills/sample-review/SKILL.md · Use when sampling recently merged PRs against repo standards and CONSTRAINTS.md. Propose environment tightenings, not…
yeachan-heo/oh-my-claudecode · skills/pr/SKILL.md · Draft a PR body from OMC's paper trail — the smallest visual that proves the change, evidence consumed from the verify…
jeremylongshore/tons-of-skills-marketplace · plugins/ai-agency/hyperflow/skills/pr/SKILL.md · Use when reviewing an incoming GitHub pull request — runs the multi-level (L1-L5) audit against the PR's real diff…
reactive/data-client · .agents/skills/pr/SKILL.md · Create a GitHub pull request from current working changes. Handles all git states - uncommitted changes, no branch…
vinta/hal-9000 · skills/pr/SKILL.md · Use when the user explicitly asks to push the current branch and open a PR, rewrite an open PR's body from its commits…
jellydn/my-ai-tools · configs/amp/plugins/my-ai-tools-skills/skills/pr/SKILL.md · Write a fast-to-review pull request body with a visual summary, before/after evidence, and merge-risk analysis.
jellydn/my-ai-tools · skills/pr/SKILL.md · Write a fast-to-review pull request body with a visual summary, before/after evidence, and merge-risk analysis.
