# Code Reviewer

> Code Reviewer

- Skill: `comcclelland/code-reviewer` (Agent Skill)
- Install (CLI): `npx skillmds@latest add comcclelland/code-reviewer`
- Raw SKILL.md: https://api.skillmd.com/api/skills/comcclelland/code-reviewer/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: comcclelland (https://skillmd.com/u/comcclelland)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/comcclelland/code-reviewer

---

# Code Reviewer

Reviews code for bugs, security vulnerabilities, logic errors, performance issues, and style violations. Organizes findings by severity and suggests fixes with code examples.

## When to Use

- Before committing or merging code
- After making significant changes to a file or module
- When the user asks to "review", "check", or "audit" code

## Process

1. Identify the scope: staged changes (`git diff --cached`), unstaged changes (`git diff`), or specific files
2. Analyze code across these dimensions:
   - **Security** — injection, XSS, auth bypasses, hardcoded secrets, unsafe deserialization
   - **Logic** — off-by-one errors, null/undefined handling, race conditions, unreachable code
   - **Performance** — unnecessary allocations, N+1 queries, blocking calls, memory leaks
   - **Edge cases** — empty inputs, boundary values, error paths, concurrent access
   - **Style** — only flag violations of the project's own established patterns

3. Organize findings by severity:
   - **Critical** — Must fix before merge (security, data loss, crashes)
   - **Warning** — Should fix (logic errors, performance, maintainability)
   - **Suggestion** — Consider fixing (minor improvements, readability)

4. For each finding, provide:
   - File path and line number
   - Description of the issue and why it matters
   - A concrete code fix in a fenced code block

## Rules

- Follow the established style and patterns of the existing codebase
- Do NOT suggest purely subjective style changes
- Do NOT comment on formatting, naming conventions, or trivial matters unless they violate project standards
- Focus on issues that genuinely matter — bugs, security, logic errors
- If no significant issues are found, say so briefly