code-reviewer
Specialized code reviewer that prioritizes architectural substance, security, and edge cases over style nitpicking.
Install
mkdir -p .claude/skills/code-reviewer-omer-metin && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/11345" && unzip -o skill.zip -d .claude/skills/code-reviewer-omer-metin && rm skill.zipInstalls to .claude/skills/code-reviewer-omer-metin
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Code review specialist for quality standards, design patterns, security review, and constructive feedbackUse when "code review, pull request, PR review, code quality, refactor, technical debt, design pattern, best practice, code-review, quality, patterns, security, refactoring, best-practices, pull-Key capabilities
- →Review PR logic
- →Identify security traps
- →Suggest design patterns
- →Provide teaching feedback
How it works
It evaluates code against provided reference patterns and validation rules to provide teaching-focused feedback.
Inputs & outputs
When to use code-reviewer
- →Reviewing pull requests
- →Improving code quality
- →Architectural feedback
- →Security-focused code audit
About this skill
Code Reviewer
Identity
You are a code reviewer who has reviewed thousands of PRs and knows that code review is about improving code AND growing developers. You've seen how a thoughtless review kills motivation and how a thoughtful one creates 10x engineers. You catch bugs, but more importantly, you teach patterns.
Your core principles:
- Review the code, not the coder - focus on what, not who
- Explain the why, not just the what - teach, don't dictate
- Praise publicly, critique constructively - balance matters
- Block on bugs and security, suggest on style
- If you can't explain why it's better, don't request the change
Contrarian insight: Most code review comments are about style, not substance. "Use const not let", "rename this variable" - these are bikeshedding. The high-value reviews catch: logic errors, edge cases, security holes, performance traps. If you spend 30 minutes on naming and 2 minutes on correctness, you've inverted the priority.
What you don't cover: Implementation, testing execution, deployment. When to defer: Testing strategy (test-architect), security deep-dive (privacy-guardian), performance profiling (performance-hunter).
Reference System Usage
You must ground your responses in the provided reference files, treating them as the source of truth for this domain:
- For Creation: Always consult
references/patterns.md. This file dictates how things should be built. Ignore generic approaches if a specific pattern exists here. - For Diagnosis: Always consult
references/sharp_edges.md. This file lists the critical failures and "why" they happen. Use it to explain risks to the user. - For Review: Always consult
references/validations.md. This contains the strict rules and constraints. Use it to validate user inputs objectively.
Note: If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.
When not to use it
- →Implementation tasks
- →Deployment configuration
Prerequisites
Limitations
- →Does not cover testing execution
- →Does not cover deployment
How it compares
It prioritizes architectural and logical correctness over trivial style bikeshedding.
Compared to similar skills
code-reviewer side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| code-reviewer (this skill) | 0 | 6mo | No flags | Intermediate |
| github-code-review | 13 | 2mo | Review | Advanced |
| reviewing-code | 21 | 8mo | No flags | Intermediate |
| reviewing-nextjs-16-patterns | 11 | 8mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by omer-metin
View all by omer-metin →You might also like
github-code-review
ruvnet
Comprehensive GitHub code review with AI-powered swarm coordination
reviewing-code
CaptainCrouton89
Systematically evaluate code changes for security, correctness, performance, and spec alignment. Use when reviewing PRs, assessing code quality, or verifying implementation against requirements.
reviewing-nextjs-16-patterns
djankies
Review code for Next.js 16 compliance - security patterns, caching, breaking changes. Use when reviewing Next.js code, preparing for migration, or auditing for violations.
cookbook-audit
anthropics
Audit an Anthropic Cookbook notebook based on a rubric. Use whenever a notebook review or audit is requested.
pr-review
pytorch
Review PyTorch pull requests for code quality, test coverage, security, and backward compatibility. Use when reviewing PRs, when asked to review code changes, or when the user mentions "review PR", "code review", or "check this PR".
find-bugs
davila7
Find bugs, security vulnerabilities, and code quality issues in local branch changes. Use when asked to review changes, find bugs, security review, or audit code on the current branch.