code-review

A code-review procedure for examining changes for bugs, security risks, performance problems, and maintainability issues. It requires reading the diff and modified files before reporting findings.

In plain words
What is it for?
Use it to review code, pull requests, or recent changes and report specific issues with file paths and line numbers.
Why use it?
It provides a focused way to catch important problems before code is merged or shipped.

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

Made for: Claude Code, Codex.

Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 302 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.00033 $0.00302
Opus 5 $0.00016 $0.00151
Sonnet 5 $0.00007 $0.00060
Haiku 4.5 $0.00003 $0.00030

Measured 3d ago against content hash e12c0f7adced, 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 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.

tutorials/pi-coding-agent-guide/resources/04-skills/code-review/SKILL.md · 48 lines

What it actually says

Code Review

When reviewing code, follow this process:

Step 1: Understand the Change

Run git diff (or git diff --staged for staged changes) to see what changed. Read the modified files in full to understand the surrounding context.

Step 2: Check for Issues

Review each changed file for:

Correctness

  • Logic errors, off-by-one errors, race conditions
  • Missing null/undefined checks at system boundaries
  • Incorrect error handling (swallowed errors, wrong error types)

Security

  • SQL injection, XSS, command injection
  • Hardcoded secrets or credentials
  • Overly permissive file/network access

Performance

  • N+1 queries, unnecessary loops, large allocations
  • Missing indexes for new database queries
  • Blocking operations in async code

Maintainability

  • Unclear naming, overly complex logic
  • Dead code, unused imports
  • Missing types in TypeScript

Step 3: Report

Format your review as:

  1. Summary: One sentence on what the change does
  2. Issues: Specific problems with file paths and line numbers
  3. Suggestions: Optional improvements (clearly marked as optional)

Be direct. Don't pad with praise. Focus on things that matter.

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. 3d ago First seen · 48 lines · 33 tokens per session scan A e12c0f7adced

Subscribe to this mod's changes

code-review is a skill published in the GitHub repository owainlewis/youtube-tutorials (375 stars, last pushed 11d ago), licensed MIT. It adds 33 tokens to every session and 302 once invoked, about $0.0002 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.