A code-review workflow for examining changed files and reporting likely bugs, security problems, performance issues, style problems, missing error handling, and test or accessibility gaps. It assigns each finding a confidence score and reports only findings rated at least 75 out of 100.

Use it to review unstaged changes or another chosen scope, check project conventions, find risks such as race conditions and security vulnerabilities, and suggest fixes for verified important issues.

It filters out findings that are probably false alarms or too minor to matter, so the review focuses on issues worth investigating.

code-review — Skill by whchoi98

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/whchoi98/project-init/code-review

Any agent

npx skills add whchoi98/project-init --skill code-review

Clone the repo

git clone --depth 1 https://github.com/whchoi98/project-init

Made for: Claude Code, Codex.

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

When invoked 340 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.

Model	Per session	Once invoked
Fable 5	$0.00000	$0.00340
Opus 5	$0.00000	$0.00170
Sonnet 5	$0.00000	$0.00068
Haiku 4.5	$0.00000	$0.00034

Measured 2d ago against content hash b4bd1a18f82d, 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 2d 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/skills/code-review/SKILL.md · 50 lines

What it actually says

Code Review Skill

Review changed code with confidence-based scoring to filter false positives.

Review Scope

By default, review unstaged changes from git diff. The user may specify different files or scope.

Review Criteria

Project Guidelines Compliance

Import patterns and module boundaries
Framework conventions and language style
Function declarations and error handling
Naming conventions from CLAUDE.md

Bug Detection

Logic errors and null/undefined handling
Race conditions and memory leaks
Security vulnerabilities (OWASP Top 10)
Performance problems

Code Quality

Code duplication and unnecessary complexity
Missing critical error handling
Test coverage gaps
Accessibility issues (for frontend code)

Confidence Scoring

Rate each issue 0-100:

0-24: Likely false positive or pre-existing issue. Do not report.
25-49: Might be real but possibly a nitpick. Do not report.
50-74: Real issue but minor. Report only if critical.
75-89: Verified real issue, important. Report with fix suggestion.
90-100: Confirmed critical issue. Must report.

Only report issues with confidence >= 75.

Output Format

For each issue:

[CRITICAL|IMPORTANT] (confidence: XX)

File: path/to/file.ext:line Issue: Clear description of the problem Guideline: Reference to CLAUDE.md rule or security standard Fix: Concrete code suggestion

If no high-confidence issues found, confirm code meets standards with brief summary.

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.

2d ago First seen · 50 lines · 0 tokens per session scan A b4bd1a18f82d

Subscribe to this mod's changes

code-review is a skill published in the GitHub repository whchoi98/project-init (2 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 340 tokens. 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.

Code review Debugging Testing

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

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

agent-host-chat-contributions

Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.

microsoft/vscode · 56 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