review SKILL.md skillA
review from dzhng/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add dzhng/skills/review@git:20261110.a7712c1Pins git:20261110.a7712c1 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- dzhng/skills
- Path
skills/review/review/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261110.a7712c1, committed Nov 10, 2026
- Size
- 1,908 bytes
- Repository stars
- 1,507
- License
- MIT
Closeout pass on a finished substantive change — sequence refactor-change (shape), code-review (diff), and write-docs (docs) so all three run, in the order where each feeds the next. Use after implementing a slice or feature and before calling it done or committing; when the user asks for a final review, a cleanup-and-document pass, or to "review everything." For a diff-only audit, reach code-review directly.
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 finished change earns "done" only after three lenses pass: its **shape**, its **diff**, and its **docs**. Each has a specialist skill. This skill owns only what they can't — the order they run in, the loop between them, and one verdict. ## Workflow 1. **Scope.** Fix the diff under review and confirm it's substantive; skip the whole pass for trivial edits. 2. **Shape — [refactor-change](../refactor-change/SKILL.md).** Run it first, while restructuring is cheap and before you audit a diff that's about to move. 3. **Diff — [code-review](../code-review/SKILL.md).** Audit the settled shape. A finding that forces a structural change sends you back to step 2, not onward. 4. **Docs — [write-docs](../../implement/write-docs/SKILL.md).** Update the docs this change touched. Then trace the link chain from the root README down to each one: every link on the path still resolves, and the hub-to-leaf flow still reads in order. 5. **Report.** One verdict across all three passes — what each found, what you changed, what you left and why. Done only when every pass is clean or resolved. ## Rules …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_map6nnb67z7t2hse/e639e48d08caa258c3aeda4b27de922a1dec31ae84ae2c662890a8154c83dd21.json
Then /plugin install review@markdownregistry-map6nnb67z7t2hse in Claude Code. It installs git:20261110.a7712c1, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add dzhng/skills/review@sha256:e639e48d08caa258The line at the top of this page pins the label git:20261110.a7712c1, 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.
[](https://markdownregistry.com/a/art_map6nnb67z7t2hse)
2 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in dzhng/skills/review since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of review from somewhere else? Ask it: where did my review come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 1 version of this file, committed on Nov 10, 2026.
Watch this file (sign in, one email per new version)
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/review/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (1908 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
dzhng/skills · 1,507 stars · license MIT · pushed 2026-11-13 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_map6nnb67z7t2hse GET https://markdownregistry.com/api/v1/resolve?ref=dzhng/skills/review GET https://markdownregistry.com/api/v1/blob/e639e48d08caa258c3aeda4b27de922a1dec31ae84ae2c662890a8154c83dd21
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.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.