code-review

A structured review of source code for problems in quality, performance, security, and testing. It reports each issue with a severity, category, location, explanation, and suggested fix.

In plain words
What is it for?
Reviewing readability, complexity, design practices, efficiency, resource use, input validation, authentication, data protection, test coverage, and edge cases.
Why use it?
It gives developers a consistent way to find defects, risky code, hard-to-maintain parts, and missing test cases before they cause problems.

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/phodal/auto-dev/code-review
Any agent
npx skills add phodal/auto-dev --skill code-review
Clone the repo
git clone --depth 1 https://github.com/phodal/auto-dev

Made for: Claude Code, Codex.

Per session 10 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 171 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.00010 $0.00171
Opus 5 $0.00005 $0.00086
Sonnet 5 $0.00002 $0.00034
Haiku 4.5 $0.00001 $0.00017

Measured yesterday against content hash 8fc5e561ccad, 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.

examples/skills/code-review/SKILL.md · 32 lines

What it actually says

Code Review

You are an experienced software engineer performing a code review.

Review Request

$ARGUMENTS

Review Criteria

  1. Code Quality: Readability, maintainability, complexity
  2. Best Practices: Design patterns, SOLID principles, DRY
  3. Performance: Efficiency, resource usage, scalability
  4. Security: Input validation, auth, data protection
  5. Testing: Test coverage, edge cases

Output Format

For each issue:

  • Severity: Critical/High/Medium/Low
  • Category: Quality/Performance/Security/Testing
  • Location: File and line
  • Issue: Description
  • Recommendation: How to fix

Project: $PROJECT_NAME

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 · 32 lines · 10 tokens per session scan A 8fc5e561ccad

Subscribe to this mod's changes

code-review is a skill published in the GitHub repository phodal/auto-dev (4,538 stars, last pushed 27d ago), licensed MPL-2.0. It adds 10 tokens to every session and 171 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-30.

Related

Other skills, from other repositories

complete-partial-pr

Evaluate and complete an issue or PR where the submitted patch fixes only a narrow symptom of the reported pain point. Use when a contribution may miss adjacent integration surfaces, provider/spec semantics, roundtrip behavior, tests, docs, or historical maintainer decisions.

pydantic/pydantic-ai · 55 tokens

testing-skill

Record, rewrite, and debug VCR cassettes for HTTP recordings. Use when running tests with --record-mode, verifying cassette playback, or inspecting request/response bodies in YAML cassettes.

pydantic/pydantic-ai · 44 tokens

adding-a-provider-api-feature

Add a new provider API capability (prompt caching, strict/structured tool calling, thinking/reasoning effort, service tier, safety settings, logprobs, etc.) to Pydantic AI. Use when wiring a provider feature through the library — it enforces reasoning from the existing cross-provider abstraction before designing…

pydantic/pydantic-ai · 97 tokens

agentfield-use

Whenever you have a discrete task to perform — one the user delegated, or one that arose inside your own work — check FIRST whether an installed AgentField agent covers it, and offload to it by default when one does. Coverage, not task size, is the test: even a small job goes to a covering agent. The check is cheap …

Agent-Field/agentfield · 259 tokens

memory

Use durable BB memory when prior project knowledge or cross-project user preferences can improve the current task, and save durable new learning through the bb memory CLI.

get-bb/bb · 32 tokens

workflows

Execute a workflow script that orchestrates multiple subagents deterministically. Use when the user explicitly requests a workflow, multi-agent orchestration, parallel or sequential agent pipelines, structured agent outputs, or a durable background workflow run.

get-bb/bb · 47 tokens