# review-spec

review-spec is a Claude Code skill that compares code with feature docs and reports mismatches in both directions. Run it mid-feature or after completion.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf (Devin Desktop), Claude.ai · ★ 155 repo stars
- Author: serpro69
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/serpro69/claude-toolbox/tree/HEAD/kodex-plugin/skills/review-spec/SKILL.md
- Updated: 2026-10-29
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/review-spec

## What it does

The skill opens the feature folder at `/docs/feat/wip/[feature]/` with `design.md`, `implementation.md` and `tasks.md` inside, then goes through the code looking for drift. Run it mid-feature to check finished tasks only, or after the whole feature is done. Mismatches surface in both directions: code that left the spec behind, and specs that no longer match the code.

Every finding carries a type (`MISSING_IMPL`, `EXTRA_IMPL`, `SPEC_DEV`, `DOC_INCON`, `OUTDATED_DOC`, `AMBIGUOUS`), a P0–P3 severity, and a confidence score from 1 to 10 with the reasoning behind it. Standard mode `$kk:review-spec` makes one pass in the current context. Isolated mode `$kk:review-spec:isolated` hands detection to a `spec-reviewer` sub-agent that never touched the code; it costs more, and a failed sub-agent sends you back to standard mode. Under an IaC profile such as Kubernetes or Terraform, the manifests count as the implementation.

None of this works without the docs in place: the three files must already sit in `/docs/feat/wip/[feature]/`. Before looking at code the skill loads the repo's convention files, `shared-capy-knowledge-protocol.md` and `shared-profile-detection.md`, and it keeps a fixed order — spec first, code after. Codex works too.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add serpro69/claude-toolbox --skill review-spec -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/review-spec/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/review-spec/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add serpro69/claude-toolbox --skill review-spec -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/review-spec/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add serpro69/claude-toolbox --skill review-spec -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/review-spec/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install serpro69/claude-toolbox kodex-plugin/skills/review-spec
```

2. **Manually: put the files in place**
- File: `.github/skills/review-spec/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add serpro69/claude-toolbox --skill review-spec -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/serpro69/claude-toolbox --path kodex-plugin/skills/review-spec
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/review-spec/SKILL.md` — The legacy .windsurf/skills/ path still works

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/serpro69/claude-toolbox/tree/HEAD/kodex-plugin/skills/review-spec/SKILL.md

## When to use it
- catch a requirement from `design.md` that never made it into the code
- spot a caching layer the specs never asked for
- check manifest values against the design in a Terraform profile
- tell a stale doc apart from a real deviation
- get a confidence score on every finding before merge

## Example prompts
- Review the feature in `/docs/feat/wip/auth/` against its design and implementation docs, run `$kk:review-spec`.
- Run `$kk:review-spec:isolated` — I want a reviewer that didn't write this code.
- Check only the finished tasks in `tasks.md` while the feature is still in progress.

## Similar
- [om-auto-implement-spec](https://affpapa.org/en/nevibecode/skills/om-auto-implement-spec.md) — skill · 4300 installs
- [gjalla-spec-review](https://affpapa.org/en/nevibecode/skills/gjalla-spec-review.md) — skill · 902 installs
- [ns-spec-driven](https://affpapa.org/en/nevibecode/skills/ns-spec-driven.md) — skill · 208 installs
- [flow-next-spec-completion-review](https://affpapa.org/en/nevibecode/skills/flow-next-spec-completion-review.md) — skill · ★ 730 repo stars
- [spec-driven-eval](https://affpapa.org/en/nevibecode/skills/spec-driven-eval.md) — skill · ★ 7191 repo stars
- [tlc-spec-driven](https://affpapa.org/en/nevibecode/skills/tlc-spec-driven.md) — skill · 1300 installs

From the same set: [serpro69/claude-toolbox](https://affpapa.org/en/nevibecode/by/serpro69/claude-toolbox.md) — 30 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
