code-reviewer

A code-review guide that checks readability, performance, security, design principles, and consistency with the existing codebase.

In plain words
What is it for?
Use it to review a diff or source files and produce improvement suggestions, optionally with revised code examples.
Why use it?
It helps identify maintainability problems, inefficient work, security risks, and departures from the project's conventions.

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/shqkel/agentic-coding/code-reviewer
Any agent
npx skills add shqkel/agentic-coding --skill code-reviewer
Clone the repo
git clone --depth 1 https://github.com/shqkel/agentic-coding

Made for: Claude Code, Codex.

Per session 48 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.

ModelPer sessionOnce invoked
Fable 5 $0.00048 $0.00340
Opus 5 $0.00024 $0.00170
Sonnet 5 $0.00010 $0.00068
Haiku 4.5 $0.00005 $0.00034

Measured yesterday against content hash 628a4607accc, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

code-reviewer 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 yesterday.

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.

04_skills/skills/code-reviewer/SKILL.md · 25 lines

What it actually says

Code Reviewer Skill

이 스킬은 코드의 품질을 높이고 유지보수성을 강화하기 위한 전문적인 코드 리뷰 가이드를 제공합니다.

리뷰 핵심 원칙

  1. 가독성 (Readability): 변수명, 함수명이 그 역할을 명확히 설명하는가?
  2. 성능 (Performance): 불필요한 연산이나 중복된 데이터베이스 쿼리가 없는가?
  3. 보안 (Security): 민감 정보 노출, SQL Injection 등 보안 취약점이 없는가?
  4. 일관성 (Consistency): 프로젝트의 기존 코딩 스타일 및 컨벤션을 따르는가?
  5. 설계 (Design): 함수가 하나의 기능만 수행하며(SRP), 의존성 관리가 적절한가?

체크리스트 (참조용)

상세한 언어별/도메인별 체크리스트는 references/checklist.md를 참고하세요.

실행 가이드

  1. 변경된 코드(git diff 또는 파일 내용)를 분석합니다.
  2. 각 원칙에 따라 개선이 필요한 부분을 식별합니다.
  3. 비판이 아닌 개선 제안(Suggestions) 형태로 피드백을 작성합니다.
  4. 가능한 경우 개선된 코드 예시를 함께 제공합니다.
Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. yesterday First seen · 25 lines · 48 tokens per session scan A 628a4607accc

Subscribe to this mod's changes

code-reviewer is a skill published in the GitHub repository shqkel/agentic-coding (2 stars, last pushed 5mo ago), licensed MIT. It adds 48 tokens to every session and 340 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-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

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 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

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens