Code Review Skill for Claude

Senior code review specialist. Use PROACTIVELY after writing or modifying code. Reviews for quality, security, performance, and best practices.

381 tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

112

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/selmakcby/claude-agents-skills --skill code-review

The instruction itself

10 sections, as written by the author

Code Review

Ne zaman tetiklenir

Yeni kod yazıldıktan hemen sonra
PR/commit öncesi
Kullanıcı "review" istediğinde

İnceleme alanları

Kalite

Clarity: İsimlendirme net mi?
Cognitive load: Fonksiyon anlamak zor mu?
Structure: Tek sorumluluk (SRP) uygulanmış mı?
Consistency: Projenin stil kılavuzuna uyuyor mu?

Doğruluk

Edge cases: null, undefined, boş dizi düşünülmüş mü?
Error handling: Try/catch doğru yerlerde mi?
Async: Promise chain'leri ve await'ler doğru mu?

Performans

N+1 queries: Veritabanı çağrılarında
O(n²) algoritmalar: Büyük dizilerde
Re-renders: React komponentlerinde

Tests

Coverage: Yeni kod için test var mı?
Missing cases: Edge case'ler test ediliyor mu?
Brittle mocks: Aşırı mocklanmış testler?

Önem seviyeleri

CRITICAL — commit edilmemeli
HIGH — sonraki release öncesi düzelt
MEDIUM — zaman olduğunda
LOW — nice-to-have

Çıktı formatı

## Kritik (must-fix)
- [dosya:satır] [sorun] [öneri]

## Yüksek
- ...

## Orta / Düşük
- ...

Kurallar

Her bulguya: önem, dosya + satır, sorun, neden önemli, nasıl düzeltilir yaz
CRITICAL bulduysan merge'i durdur
Sadece sorunu değil, çözümü de söyle

Other skills for the same job

different authors, same section of the catalogue

Receiving Code Review

by ZhanlinCui

×7

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

2k tokens

Requesting Code Review

by ZhanlinCui

×6

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping

Comprehensive GitHub code review with AI-powered swarm coordination

Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.

Use this skill to review code. It supports both local changes (staged or working tree) and remote Pull Requests (by ID or URL). It focuses on correctness, maintainability, and adherence to project standards.

Refactor bloated AGENTS.md, CLAUDE.md, or similar agent instruction files to follow progressive disclosure principles. Splits monolithic files into organized, linked documentation.

Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits). Use when the user asks to commit, craft a commit message, stage changes, or split work into multiple commits.

2k tokens

How to use it

Copy the folder

Take selmakcby/claude-agents-code-review from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.