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.

Install it, pinned
mdr add alexisbalayre/claude-code-config/.claude/agents/review-spec.md@git:20261017.c5ad833

Pins 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

The exact contents, by fingerprint
mdr add alexisbalayre/claude-code-config/.claude/agents/review-spec.md@sha256:3106300af3f20234

The 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.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_ibmerooawnkharg5.svg)](https://markdownregistry.com/a/art_ibmerooawnkharg5)

1 badge image fetches in 30 days. What the badge shows.

Ask from your agent
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)

versioncommittedcommitsizeaudit
git:20261017.c5ad833 latest2026-10-17 c5ad833 2,762 BA view
Check a whole project

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

A  14 of 14 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • 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

GitHub

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

README Claude Code subagent
alexisbalayre/claude-code-config · .claude/agents/README.md
git:20261017.c5ad833 · audit A · 3 stars
architecture-explainer Claude Code subagent
alexisbalayre/claude-code-config · .claude/agents/architecture-explainer.md · Use PROACTIVELY when the user asks why or how about the system architecture — component boundaries, data flow, request…
git:20260917.a589e3f · audit A · 3 stars
comment-pruner Claude Code subagent
alexisbalayre/claude-code-config · .claude/agents/comment-pruner.md · Autonomously prune bad comments from code added in the current session. Dispatched by the comment-pruner Stop hook when…
git:20260917.a589e3f · audit A · 3 stars
convention-checker Claude Code subagent
alexisbalayre/claude-code-config · .claude/agents/convention-checker.md · Use PROACTIVELY to verify files follow area-specific coding standards before committing. MUST BE USED after editing…
git:20260917.a589e3f · audit A · 3 stars
migration-reviewer Claude Code subagent
alexisbalayre/claude-code-config · .claude/agents/migration-reviewer.md · Use PROACTIVELY after any change to database schema definitions (ORM models, schema files) or to migration files (new…
git:20260917.a589e3f · audit A · 3 stars
review-context Claude Code subagent
alexisbalayre/claude-code-config · .claude/agents/review-context.md · Reviews changed code for spec contradictions, protocol violations, and infrastructure anti-patterns. Spawned by the…
git:20260811.6af4418 · audit A · 3 stars
review-conventions Claude Code subagent
alexisbalayre/claude-code-config · .claude/agents/review-conventions.md · Audits changed files for compliance with the project's documented rules and accepted ADR decisions. Spawned by the…
git:20260917.a589e3f · audit A · 3 stars
review-correctness Claude Code subagent
alexisbalayre/claude-code-config · .claude/agents/review-correctness.md · Reviews changed code for logic and behavior defects that deterministic tooling cannot catch, including behavioral…
git:20261017.279b6aa · audit A · 3 stars
review-docs Claude Code subagent
alexisbalayre/claude-code-config · .claude/agents/review-docs.md · Reviews the quality, accuracy, and usefulness of prose a change introduces. Strict on low-value comments and…
git:20260917.a589e3f · audit A · 3 stars
review-maintainability Claude Code subagent
alexisbalayre/claude-code-config · .claude/agents/review-maintainability.md · Reviews changed code for structural regressions that make the codebase harder to maintain. Spawned by the pr-ci-review…
git:20261017.c5ad833 · audit A · 3 stars
review-security Claude Code subagent
alexisbalayre/claude-code-config · .claude/agents/review-security.md · Reviews changed code for real, reachable security issues at system boundaries. Spawned by the pr-ci-review skill.
git:20261017.279b6aa · audit A · 3 stars
review-validator Claude Code subagent
alexisbalayre/claude-code-config · .claude/agents/review-validator.md · Adversarially verifies review findings against the actual code, refuting the ones that do not hold. Spawned by the…
git:20261005.2d3e564 · audit A · 3 stars

Every file in alexisbalayre/claude-code-config

Other files named review-spec

review-spec SKILL.md skill
sd0xdev/sd0x-harness · skills/review-spec/SKILL.md · Review technical spec documents from completeness, feasibility, risk, and code consistency perspectives.
git:20260905.d98c025 · audit A · 196 stars
review-spec SKILL.md skill
serpro69/claude-toolbox · kodex-plugin/skills/review-spec/SKILL.md · Use after implementing tasks or mid-feature to verify code matches design docs and ensure they are in sync. Detects…
git:20260910.562e70a · audit A · 155 stars
review-spec SKILL.md skill
serpro69/claude-toolbox · klaude-plugin/skills/review-spec/SKILL.md · Use after implementing tasks or mid-feature to verify code matches design docs and ensure they are in sync. Detects…
git:20260910.562e70a · audit A · 155 stars
review-spec SKILL.md skill
sergeyklay/.agents · .agents/skills/review-spec/SKILL.md · Architectural review of a specification or design document, performed before implementation begins. Use whenever a spec…
v2.1 · audit A · 6 stars

Browse by kind, by grade A, or by owner.