Download for MacApple silicon, macOS 14+
Skill

code-reviewer

@jeffallan Updated 2026-10-30

Analyzes code diffs and files to identify bugs, security vulnerabilities (SQL injection, XSS, insecure deserialization), code smells, N+1 queries, naming issues, and architectural concerns, then produces a structured review report with prioritized, actionable feedback. Use when reviewing pull requests, conducting code quality audits, identifying refactoring opportunities, or checking for security issues. Invoke for PR reviews, code quality checks, refactoring suggestions, review code, code quality. Complements specialized skills (security-reviewer, test-master) by providing broad-scope review across correctness, performance, maintainability, and test coverage in a single pass.

ai-agentsclaudeclaude-codeclaude-marketplaceclaude-skills

Install

With your agent

Install OMGSkills skill "jeffallan/claude-skills:code-reviewer" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.

Manual command

git clone https://github.com/Jeffallan/claude-skills /tmp/claude-skills && ln -s /tmp/claude-skills/skills/code-reviewer ~/.claude/skills/code-reviewer

From README

Code Reviewer Senior engineer conducting thorough, constructive code reviews that improve quality and share knowledge. When to Use This Skill Reviewing pull requests Conducting code quality audits Identifying refactoring opportunities Checking for security vulnerabilities Validating architectural decisions Core Workflow Context — Read PR description, understand the problem being solved. Checkpoint: Summarize the PR's intent in one sentence before proceeding. If you cannot, ask the author to clarify. Structure — Review architecture and design decisions. Ask: Does this follow existing patterns in the codebase? Are new abstractions justified? Details — Check code quality, security, and performance. Apply the checks in the Reference Guide below. Ask: Are there N+1 queries, hardcoded secrets, or injection risks? Tests — Validate test coverage and quality. Ask: Are edge cases covered? Do tests assert behavior, not implementation?