A review procedure for examining source code, changes, or a whole project before release. It determines the review scope, detects the technologies used, and checks the code systematically.

Use it to review selected files, recent Git changes, or an entire codebase with attention to important and recently changed areas.

It helps find defects, security or design risks, and maintenance problems before code is shipped.

code-review — Skill for Claude Code by kimon1230/claude

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 kimon1230/claude_extensions --skill code-review

Clone the repo

git clone --depth 1 https://github.com/kimon1230/claude_extensions

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/kimon1230/claude_extensions/code-review/github.svg)](https://agentmods.dev/skills/kimon1230/claude_extensions/code-review)

Your own site

<a href="https://agentmods.dev/skills/kimon1230/claude_extensions/code-review"><img src="https://agentmods.dev/badge/skills/kimon1230/claude_extensions/code-review/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/kimon1230/claude_extensions/code-review"><img src="https://agentmods.dev/badge/skills/kimon1230/claude_extensions/code-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 41 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 3,945 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.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00041	$0.03945
Opus 5.5	$0.00016	$0.01578
Sonnet 5.5	$0.00008	$0.00789
Haiku 4.5	$0.00004	$0.00394

Measured 3d ago against content hash 0e602404363c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 3d 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 · 189 lines

How it starts

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

Code Review

This skill must only be invoked from the main session, never from a subagent.

1. Determine Scope

a. If the user specified file paths, directories, or a description of what to review, use that as the scope. b. If the user said "review my changes" or similar, use git diff HEAD (unstaged + staged) and git diff --cached as the scope. Include full file context for changed functions, not just the diff hunks. If no changes exist, tell the user and stop. c. If no scope is specified, ask the user: "What should I review? Options: specific files/directories, recent changes (git diff), or the entire project." d. For entire-project scope, identify all source files (exclude vendored/generated code, build artifacts, lock files, and test fixtures). Prioritize by architectural significance: import fan-in/fan-out, file size, and recent change frequency. Distribute files across agents by relevance to each agent's domain. e. Confirm scope with the user before proceeding: "I'll code-review [scope description]. Correct?"

Language & Project Detection

After determining scope, detect the primary language(s) and framework(s):

Check file extensions, lock files (package-lock.json, Pipfile.lock, Cargo.lock), and config/module files (tsconfig.json, pyproject.toml, Cargo.toml, go.mod, go.sum)
Set primary_language and note the framework(s) in use
Inform user: "Detected [language] project using [framework] — tailoring review accordingly."
Check for project-level or user-level rule files (rules/<language>.md, e.g., rules/python.md) and instruct agents to read them if present for project-specific conventions.

Language detection shapes agent behavior — agents should apply language-idiomatic checks:

Python: mutable default arguments, bare except:, missing type hints on public APIs, os.path vs pathlib
JavaScript/TypeScript: == vs ===, var usage, unhandled promise rejections, missing async/await error handling, prototype pollution patterns
Go: unchecked errors, goroutine leaks, missing defer for cleanup, context propagation
Rust: unnecessary .clone(), missing error propagation with ?, overly broad lifetimes
Java: checked exception abuse, mutable DTOs, missing @Override, raw types
Other languages: apply general software engineering principles

Read the full file on GitHub · 189 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.

3d ago Changed · +18 tokens per session 0e602404363c
1mo ago First seen · 189 lines · 23 tokens per session scan A c673e0fcbfbf

Subscribe to this mod's changes

code-review is a skill published in the GitHub repository kimon1230/claude_extensions (4 stars, last pushed 2d ago), licensed MIT. It adds 41 tokens to every session and 3,945 once invoked, about $0.0002 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-31.

Claude Code Code review ai-coding claude-code-extensions claude-code-hooks claude-code-skills developer-tools

dev-cycle

Run a requested full development workflow: branch, implement, check, review, PR, merge, and release.

iuliandita/skills · 25 tokens

skill-refiner

Improve skills through repeated scoring, behavioral tests, and peer review toward a requested quality target.

iuliandita/skills · 22 tokens

code-reviewer

Code review knowledge base: quality, security (OWASP Top 10), error-handling, performance, and test-coverage checklists with severity-ranked output format. Use when reviewing code changes, PRs, or before commits. Loaded automatically by the code-reviewer agent.

claude-world/director-mode-lite · 59 tokens

code-review