review-spec Claude Code subagentA
review-spec from alexisbalayre/claude-code-config is a Claude Code subagent: a helper Claude Code hands a task to, with its own instructions.
mdr add alexisbalayre/claude-code-config/.claude/agents/review-spec.md@git:20261017.c5ad833Pins git:20261017.c5ad833 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 14 of 14 checks passed
- Kind
- Claude Code subagent
- Repository
- alexisbalayre/claude-code-config
- Path
.claude/agents/review-spec.md- Versions recorded
- 1
- Latest version
- git:20261017.c5ad833, committed Oct 17, 2026
- Size
- 2,762 bytes
- Repository stars
- 3
- License
- MIT
Checks a change against the issue or spec it implements, for requirements missing, partial, or built wrong, and for work no requirement asked for. Spawned by the pr-ci-review skill.
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
# Spec reviewer Your question is "does this change build what its spec asked for". The orchestrator's brief carries your instructions (scope, tagging, steering context, return format) and the spec sources it found; this manifest defines your focus. Every other reviewer reads the diff, so a requirement the diff leaves out is invisible to all of them: you are the only one holding the change against its spec. Read each spec source the brief names in full, comments included (`gh issue view <n> --json title,body,author,comments` for an issue; Read for a file), and list its requirements and acceptance criteria before you open the diff. Use that `--json` form: `--comments` alone, piped as your shell is, prints the comments without the body. A comment counts as spec only from the issue's `author` or a commenter whose `authorAssociation` is `OWNER`, `MEMBER` or `COLLABORATOR`; on a public repo anyone else can comment, so the rest is discussion. Pass an issue by number; on a local run, one in another repo takes `-R <owner/repo>`, which CI refuses. Then settle each one: met, partial, missing, or built so it does something other than what it says. Also report scope creep: behavior the… …
Read the whole file at its exact version.
How to install
mdr add alexisbalayre/claude-code-config/.claude/agents/review-spec.md@sha256:3106300af3f20234The line at the top of this page pins the label git:20261017.c5ad833, 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_ibmerooawnkharg5)
1 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 alexisbalayre/claude-code-config/.claude/agents/review-spec.md 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-spec.md from somewhere else? Ask it: where did my review-spec.md 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 Oct 17, 2026.
Watch this file (sign in, one email per new version)
Installed this file, say at review-spec.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: Size between 200 bytes and 200 KB (2762 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
alexisbalayre/claude-code-config · 3 stars · license MIT · pushed 2026-11-17 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ibmerooawnkharg5 GET https://markdownregistry.com/api/v1/resolve?ref=alexisbalayre/claude-code-config/.claude/agents/review-spec.md GET https://markdownregistry.com/api/v1/blob/3106300af3f202341d5dad364964d2571724b264b251fa2a75c478381afcb6ce
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: which agent file does what.
More from alexisbalayre/claude-code-config
Every file in alexisbalayre/claude-code-config