code-review

A structured review step for Spec Kit projects, where written specifications guide implementation. It can review documentation, code, or tests at different points in the development process.

In plain words
What is it for?
Use it to review specification documents, check code against the constitution and plan, or assess test quality and alignment with the specification.
Why use it?
It helps find missing requirements, implementation differences, weak documentation, and gaps in test coverage before work is considered complete.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/stefaniuk/loadout/code-review
Any agent
npx skills add stefaniuk/loadout --skill code-review
Clone the repo
git clone --depth 1 https://github.com/stefaniuk/loadout

Made for: Claude Code, Codex.

Per session 29 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,279 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00029 $0.01279
Opus 5 $0.00015 $0.00639
Sonnet 5 $0.00006 $0.00256
Haiku 4.5 $0.00003 $0.00128

Measured yesterday against content hash 6eb9a0c7772f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

code-review scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.github/skills/code-review/SKILL.md · 109 lines

How it starts

The opening of the file, as written. The whole thing — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Code Review Skill

This skill runs a structured review within the Spec Kit pipeline. It supports three review types, each with a distinct focus and output format.

Review Type Resolution

Resolve the review type from the user's input ($ARGUMENTS). Match against the table below.

Type Role Focus Position in pipeline
documentation Product Owner Spec integrity, traceability, language, structure, redundancy, cross-document alignment After spec + plan, before implementation
code Implementation Engineer Constitution compliance, specification coverage, discrepancy detection, plan/tasks alignment After implementation, before test review
test Implementation Engineer Test pyramid health, unit test quality, high-value gaps, spec alignment, test refactoring After code review

If the review type is not in this table, inform the user and list the supported types.

Mandatory Context Gathering

For all review types:

  1. Read the constitution - it has the highest authority.
  2. Enumerate available artefacts in the specs/ directory of the current feature.
  3. Read the spec set in feature order: spec.mdplan.mdtasks.md.
  4. Read any relevant ADRs in docs/adr/.

Additional Context by Type

documentation: Also read docs/ directory contents and README.md for cross-document alignment checks.

code: Build a behaviour inventory mapping constitution rules → spec requirements → implementation code → test coverage. Identify any gaps.

test: Execute make test and review the output. Analyse the test pyramid (unit, integration, end-to-end) and identify coverage gaps.

Read the full file on GitHub · 109 lines

Files

What ships with it

5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 109 lines · 29 tokens per session scan A 6eb9a0c7772f

Subscribe to this mod's changes

code-review is a skill published in the GitHub repository stefaniuk/loadout (1 stars, last pushed 3d ago), licensed MIT. It adds 29 tokens to every session and 1,279 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.