agentmods.dev

code-review

code-review is a skill for Claude Code from itsnex1s/awesome-claude-skills. It costs 23 tokens per session (1,313 once invoked), scanned A, original, MIT.

A set of guidelines for checking code changes before they are merged into a shared codebase.

In plain words
What is it for?
Use it to review features, refactoring, new dependencies, and security-sensitive changes, or to request feedback before merging.
Why use it?
It helps catch bugs, missing edge cases, poor error handling, and hard-to-read code earlier.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

not rated 5repo 8mo ago A scan 23 tokens original MIT

Good fit Use it to review features, refactoring, new dependencies, and security-sensitive changes, or to request feedback before merging.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/itsnex1s/awesome-claude-skills/code-review
View source ↗ itsnex1s/awesome-claude-skills
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 itsnex1s/awesome-claude-skills --skill code-review
Clone the repo
git clone --depth 1 https://github.com/itsnex1s/awesome-claude-skills

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.

agentmods badge for code-review

README.md
[![agentmods](https://agentmods.dev/badge/skills/itsnex1s/awesome-claude-skills/code-review/github.svg)](https://agentmods.dev/skills/itsnex1s/awesome-claude-skills/code-review)
Your own site
<a href="https://agentmods.dev/skills/itsnex1s/awesome-claude-skills/code-review"><img src="https://agentmods.dev/badge/skills/itsnex1s/awesome-claude-skills/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.

agentmods 80×15 button for code-review

Your own site · 80×15
<a href="https://agentmods.dev/skills/itsnex1s/awesome-claude-skills/code-review"><img src="https://agentmods.dev/badge/skills/itsnex1s/awesome-claude-skills/code-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 23 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,313 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00023 $0.01313
Opus 5.5 $0.00009 $0.00525
Sonnet 5.5 $0.00005 $0.00263
Haiku 4.5 $0.00002 $0.00131

Measured 2mo ago against content hash a95e6a14acfa, 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 2mo 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 · 247 lines

How it starts

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

code-review

Guidelines for requesting and performing code reviews effectively.

Core Principle

Review early, review often - catch issues before they escalate.

When to Request Review

Mandatory Reviews

  • After completing individual tasks in workflows
  • After finishing major features
  • Before merging to main branch
  • After significant refactoring

Recommended Reviews

  • Every 3 tasks in a longer workflow
  • When unsure about implementation approach
  • After adding new dependencies
  • When touching security-sensitive code

How to Request Review

Get Commit Context

# Recent commits
git log --oneline -10

# Diff from main
git diff main..HEAD

# Changed files
git diff --name-only main..HEAD

# Specific commit
git show <commit-hash>

Provide Context

When requesting review, include:

  1. What changed and why
  2. Areas of concern or uncertainty
  3. Testing done
  4. Related issues/PRs

Review Checklist

Functionality

  • Code does what it's supposed to do
  • Edge cases are handled
  • Error handling is appropriate
  • No obvious bugs or logic errors

Code Quality

  • Code is readable and self-documenting
  • Functions/methods are focused (single responsibility)
  • No unnecessary complexity
  • DRY - no significant duplication
  • Naming is clear and consistent

Security

  • No hardcoded secrets
  • Input validation present
  • SQL injection prevention
  • XSS prevention
  • Auth/permissions checked

Performance

  • No N+1 queries
  • No unnecessary re-renders (React)
  • Expensive operations are optimized
  • Caching used where appropriate

Testing

  • Tests cover new functionality
  • Tests cover edge cases
  • Existing tests still pass
  • Test names are descriptive

Style & Conventions

  • Follows project coding standards
  • Consistent with surrounding code
  • Linting passes
  • TypeScript types are appropriate

Severity Levels

🔴 Critical (Must Fix Now)

  • Security vulnerabilities
  • Data loss potential
  • Crashes or major bugs
  • Breaking changes without migration

Read the full file on GitHub · 247 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. 2mo ago First seen · 247 lines · 23 tokens per session scan A a95e6a14acfa

Subscribe to this mod's changes

code-review is a skill published in the GitHub repository itsnex1s/awesome-claude-skills (5 stars, last pushed 8mo ago), licensed MIT. It adds 23 tokens to every session and 1,313 once invoked, about $0.0001 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 CodeCode reviewaiawesomeclaudeclideveloper-tools
Related

code-review compared with skills from other repositories

code-review next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
code-reviewitsnex1s/awesome-claude-skillsSkill58mo agoMITA23Claude Code
find-simplificationsQwenLM/qwen-codeSkill29ktodayApache-2.0C103Claude Code, Codex
gitnexushashgraph-online/awesome-codex-pluginsSkill1.5kyesterdayApache-2.0A58Codex
swarm-pr-reviewZaxbyHub/opencode-swarmSkill518todayMITA91Claude Code
include-test-files-that-assert-on-behavior-being-changed-in-declZaxbyHub/opencode-swarmSkill518todayMITA29OpenCode
code-reviewjrswab/axeSkill90917d agoApache-2.0A0Claude Code, Codex
agent-debug-ciNVIDIA/elementsSkill115yesterdayApache-2.0A80Claude Code, Codex