Quality review of a change: is the logic right, is it safe, does it hold under real load, is risky code tested, is it fast enough, and is every line needed. Reads the connected code, not only the diff. Each finding is explained in plain English. Use for "review this", "code review", "review the last commit", "review my PR", "is this over-engineered", /ponytail-review.
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
Review a change like the senior developer who will be paged when it breaks.
Order of importance: correct, safe, holds under load, tested, fast, lean.
Lean still matters: every extra line must be read, tested and fixed later.
This is a report the user asked for, so give it in full.
## 1. Understand first
- Review what the user names: uncommitted or staged changes, a branch, a PR
link, or files. Nothing named: the uncommitted changes, or the last commit
if there are none.
- Read the diff, then the code it touches: callers of every changed function,
the functions it calls, the tests, the README.
- Trace the real flow: where data comes in, what is stored, what goes out.
- A change can break code it does not touch. When a signature, return value
or behavior changes, grep every caller.
- Find the expected load in the repo (README, deploy config): one person
running a script, or many users and processes at once. Judge scale against
that, and say which load you assumed.
## 2. Look for
1. **Bug:** wrong result, crash, missed edge case (empty, zero, last item,
rounding, time zones), a caller broken by the change, a fix applied in one
…
The line at the top of this page pins the label git:20261012.178eb1e, 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.
A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (5170 bytes)
pass: No zero-width or bidi control characters
pass: No instruction hidden inside an HTML comment
pass: No link to an exfiltration or paste host
pass: No credential-shaped string
pass: No instruction to send local credentials anywhere
pass: No text hidden with inline styles
pass: No prompt-injection phrasing
pass: No curl or wget piped into a shell
pass: No recursive delete of root, home or parent
pass: No instruction to read or print local credentials
pass: No base64 blob over 200 characters
pass: No link to a raw IP address
pass: No script tag
Source
GitHub
shaderera/shaderera · 7 stars · license MIT · pushed 2026-10-31 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_jqj2atsd3b3egkf2
GET https://markdownregistry.com/api/v1/resolve?ref=shaderera/shaderera/ponytail-review
GET https://markdownregistry.com/api/v1/blob/a3c21555db2eacaa89ad40affbbc3f063c90aed44fb6fb0d41472d1140d60c70
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.
shaderera/shaderera · .claude/skills/code-review/SKILL.md · Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code…
shaderera/shaderera · .claude/skills/codebase-design/SKILL.md · Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find…
shaderera/shaderera · .claude/skills/diagnosing-bugs/SKILL.md · Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports…
shaderera/shaderera · .claude/skills/domain-modeling/SKILL.md · Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md…
shaderera/shaderera · .claude/skills/grill-with-docs/SKILL.md · A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
shaderera/shaderera · .claude/skills/grilling/SKILL.md · Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or…
shaderera/shaderera · .claude/skills/improve-codebase-architecture/SKILL.md · Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you…
dietrichgebert/ponytail · .openclaw/skills/ponytail-review/SKILL.md · Quality review of a diff: bugs, security, real load, missing tests, speed, and what to delete. Each finding says what…
dietrichgebert/ponytail · skills/ponytail-review/SKILL.md · Quality review of a change: is the logic right, is it safe, does it hold under real load, is risky code tested, is it…
kunolu/640-skills · sbtd-workflow-onboard/assets/external-skills/stable/skills/ponytail-review/SKILL.md · Quality review of a change: is the logic right, is it safe, does it hold under real load, is risky code tested, is it…
dmae97/omk · .omk/skills/ponytail-review/SKILL.md · Code review focused exclusively on over-engineering. Finds what to delete: reinvented standard library, unneeded…
wildcard/caro · .claude/skills/ponytail-review/SKILL.md · Run the pragmatic-skeptic 'ponytail' reviewer over the current diff to surface over-engineering — code, abstractions…
djarvur/go-ultimate · skills/ponytail-review/SKILL.md · Quality review of a change: is the logic right, is it safe, does it hold under real load, is risky code tested, is it…
fahthiz/oasis · skills/ponytail-review/SKILL.md · Quality review of a change: is the logic right, is it safe, does it hold under real load, is risky code tested, is it…