code-review

code-review is a skill for Claude Code, Codex from ao92265/claude-code-playbook. It costs 82 tokens per session (827 once invoked), scanned A, original, MIT.

A structured review of recent code changes. It looks for bugs, security problems, performance issues, and style concerns, then labels findings by severity and explains how to act on them.

In plain words
What is it for?
Use it to review unstaged changes, staged changes, or the latest commit. It is for your own code changes, not for reviewing other people's pull requests or security-only assessments.
Why use it?
It gives a consistent way to check a diff, the set of code changes, before committing or releasing it. This helps surface serious defects and edge cases that ordinary reading may miss.

Skill for Claude CodeCodex

Part of the playbook plugin — 49 skills, 4 hooks shipped together

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

Made for: Claude Code, Codex.

Or install playbook, the plugin that ships this one along with the rest of its 49 skills, 4 hooks.

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 code-review

README.md
[![agentmods](https://agentmods.dev/badge/skills/ao92265/claude-code-playbook/code-review.svg)](https://agentmods.dev/skills/ao92265/claude-code-playbook/code-review)
Your own site
<a href="https://agentmods.dev/skills/ao92265/claude-code-playbook/code-review"><img src="https://agentmods.dev/badge/skills/ao92265/claude-code-playbook/code-review.svg" alt="Measured on agentmods" height="20"></a>
Per session 82 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 827 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.00082 $0.00827
Opus 5 $0.00041 $0.00413
Sonnet 5 $0.00016 $0.00165
Haiku 4.5 $0.00008 $0.00083

Measured 4d ago against content hash 310aae47f024, 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 4d 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.

skills/code-review/SKILL.md · 96 lines

How it starts

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

Code Review

Structured review of recent code changes with severity ratings and actionable feedback.

Steps

  1. Identify scope:

    • Get recent changes: git diff (unstaged), git diff --cached (staged), or git diff HEAD~1 (last commit)
    • Ask the user if a different scope is needed
    • List all changed files and total lines changed
  2. Review for correctness (Critical/High):

    • Logic errors: off-by-one, wrong comparisons, missing null checks
    • Race conditions in async/concurrent code
    • Resource leaks: unclosed connections, missing cleanup
    • Error handling: swallowed errors, missing catch blocks, wrong error types
    • Edge cases: empty arrays, zero values, undefined, boundary conditions
  3. Review for security (Critical/High):

    • Injection vulnerabilities (SQL, command, template)
    • XSS: unescaped user input in output
    • Hardcoded secrets or credentials
    • Missing authentication or authorization checks
    • Insecure defaults (permissive CORS, debug mode)
  4. Review for performance (Medium):

    • N+1 queries or unnecessary database calls
    • Missing pagination on list endpoints
    • Blocking operations in async contexts
    • Unnecessary re-renders in React components
    • Large objects in memory that could be streamed
  5. Review for maintainability (Low/Medium):

    • Functions exceeding ~50 lines
    • Deeply nested conditionals (3+ levels)
    • Duplicated logic that should be extracted
    • Misleading variable or function names
    • Missing type annotations on public APIs
  6. Review for testing (Medium):

    • New code paths without corresponding tests
    • Modified behavior without updated tests
    • Test assertions that don't actually verify the behavior
    • Missing edge case tests for error handling
  7. Format the review:

    ## Code Review Summary
    
    **Files reviewed:** X | **Issues found:** Y
    
    ### Critical
    - [file:line] [description] — [suggestion]
    
    ### High
    - [file:line] [description] — [suggestion]
    
    ### Medium
    - [file:line] [description] — [suggestion]
    
    ### Low
    - [file:line] [description] — [suggestion]
    
    ### Positive
    - [what was done well]
    

Read the full file on GitHub · 96 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. 4d ago First seen · 96 lines · 82 tokens per session scan A 310aae47f024

Subscribe to this mod's changes

code-review is a skill published in the GitHub repository ao92265/claude-code-playbook (10 stars, last pushed 17d ago), licensed MIT. It adds 82 tokens to every session and 827 once invoked, about $0.0004 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens