review-code

review-code is a skill for Claude Code from doodledood/manifest-dev. It costs 101 tokens per session (2,172 once invoked), scanned A, original, MIT.

A focused code-review process that checks one quality area at a time, such as bugs, design, tests, types, documentation, or operational readiness.

In plain words
What is it for?
Use it to review a code change for defects, maintainability, test quality, type safety, contracts, documentation, or another selected dimension.
Why use it?
It prevents broad, unfocused reviews by defining what to inspect and what a change must satisfy to pass.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter.

Part of the manifest-dev plugin — 19 skills shipped together

Good fit Use it to review a code change for defects, maintainability, test quality, type safety, contracts, documentation, or another selected dimension.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/doodledood/manifest-dev/review-code
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.

Any agent
npx skills add doodledood/manifest-dev --skill review-code
Clone the repo
git clone --depth 1 https://github.com/doodledood/manifest-dev

Made for: Claude Code.

Or install manifest-dev, the plugin that ships this one along with the rest of its 19 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for review-code

README.md
[![agentmods](https://agentmods.dev/badge/skills/doodledood/manifest-dev/review-code/github.svg)](https://agentmods.dev/skills/doodledood/manifest-dev/review-code)
Your own site
<a href="https://agentmods.dev/skills/doodledood/manifest-dev/review-code"><img src="https://agentmods.dev/badge/skills/doodledood/manifest-dev/review-code/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for review-code

Your own site · 80×15
<a href="https://agentmods.dev/skills/doodledood/manifest-dev/review-code"><img src="https://agentmods.dev/badge/skills/doodledood/manifest-dev/review-code.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 101 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,172 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.1 $0.00101 $0.02172
Opus 5.5 $0.00040 $0.00869
Sonnet 5.5 $0.00020 $0.00434
Haiku 4.5 $0.00010 $0.00217

Measured 9d ago against content hash 29e8a03f181d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

review-code 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 9d ago.

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.

claude-plugins/manifest-dev/skills/review-code/SKILL.md · 102 lines

How it starts

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

review-code — one dimension per invocation

Audit a change along one review dimension and report findings. Load only that dimension's reference.

Input

$ARGUMENTS carries the dimension plus optional scope, e.g. dimension=code-bugs or code-bugs src/foo.ts. A manifest gate's body activates this skill with the dimension under /do's selected evaluator; the gate names the dimension and this skill owns the threshold. If no dimension is given, list the available dimensions and ask which one — one invocation, one dimension.

Dimensions and thresholds

Load references/<dimension>.md for the requested dimension and follow it. Its standards are opinionated defaults: where a rule the user stated, in the session or a context file, or a convention the project states or documents (not a pattern its code merely repeats) differs, that rule governs, a change following it raises no finding, and the report names the rule applied — except a Critical finding on the ladder below, which is still reported, naming the rule that produced it. The threshold is the bar a change must clear to PASS on that dimension:

Dimension Reference Role Threshold (PASS requires)
change-intent references/change-intent.md defect-finder no LOW-or-higher findings
code-bugs references/code-bugs.md defect-finder no LOW-or-higher findings
contracts references/contracts.md defect-finder no LOW-or-higher findings
type-safety references/type-safety.md defect-finder no LOW-or-higher findings
defect-class references/defect-class.md defect-finder no LOW-or-higher findings
operational-readiness references/operational-readiness.md advisory no MEDIUM-or-higher findings
code-design references/code-design.md advisory no MEDIUM-or-higher findings
code-maintainability references/code-maintainability.md advisory no MEDIUM-or-higher findings
code-simplicity references/code-simplicity.md advisory no MEDIUM-or-higher findings
code-testability references/code-testability.md advisory no MEDIUM-or-higher findings
test-quality references/test-quality.md advisory no MEDIUM-or-higher findings
docs references/docs.md advisory no MEDIUM-or-higher findings
prose-value references/prose-value.md advisory no MEDIUM-or-higher findings
context-file-adherence references/context-file-adherence.md advisory no MEDIUM-or-higher findings

Read the full file on GitHub · 102 lines

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. 9d ago Changed 29e8a03f181d
  2. 27d ago Changed 119a15f18c8b
  3. 1mo ago Changed 03b95c3450cf
  4. 1mo ago Changed · -2 tokens per session c7b57e392bb8
  5. 1mo ago First seen · 102 lines · 103 tokens per session scan A f10f15c87574

Subscribe to this mod's changes

review-code is a skill published in the GitHub repository doodledood/manifest-dev (75 stars, last pushed yesterday), licensed MIT. It adds 101 tokens to every session and 2,172 once invoked, about $0.0004 per session on Opus 5.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-30.

Related

Other skills, from other repositories

great_cto

Use when the CTO describes a feature, task, or project goal. Orchestrates the full SDLC pipeline automatically based on project type.

avelikiy/great_cto · 32 tokens

opportunity-solution-tree

Build an Opportunity Solution Tree (OST) to structure product discovery — map a desired outcome to customer opportunities, possible solutions, and experiments. Based on Teresa Torres' Continuous Discovery Habits. Use when the team is unclear what to build next, when multiple opportunities compete, or before writing a…

avelikiy/great_cto · 71 tokens

skeptical-triage

Reusable 3-round self-challenge + arbiter pattern for filtering false positives from findings/verdicts. Use when the cost of a false-positive gate block exceeds the cost of 4 extra LLM turns.

avelikiy/great_cto · 49 tokens

anti-patterns

Catalogue of known SDLC anti-patterns that greatcto agents must actively reject when reviewing architecture, plans, code, or post-mortems. Used by architect (pre-impl), pm (planning), senior-dev (impl), l3-support (post-incident).

avelikiy/great_cto · 59 tokens

cost-model

Standardized cost-estimation framework for greatcto plans. Forces explicit LLM cost, infra cost, human-supervision time, and the (defensible) human-equivalent comparison. Output format is parsable by the board's /api/cost path — must follow exactly.

avelikiy/great_cto · 59 tokens

done-blocked

Reusable reporting contract for any agent that hands work back to the pipeline. Forces ONE of two terminal statuses (DONE or BLOCKED) with a specific evidence shape. Stops vague "probably finished" and "kind of stuck" verdicts.

avelikiy/great_cto · 51 tokens