Code Review Skill

Perform a thorough, opinionated code review of a project or set of files. The goal is to find real problems that matter — not nitpick formatting or chase theoretical issues. Think like a senior dev doing a PR review of an entire codebase, with a security engineer looking over your shoulder.

Philosophy

Be useful, not exhaustive. A review that lists 200 minor issues is worse than one that identifies the 10 things that actually matter. Prioritize by impact: bugs > security > architecture > maintainability > style.

Be specific, not vague. "This code could be better" helps nobody. "The retry logic in api/client.ts:34 swallows errors silently — failed requests disappear without logging or propagation" is actionable.

Show, don't just tell. When suggesting improvements, include a brief code example of what the fix looks like. Don't rewrite everything — just enough to communicate the pattern.

Security is not optional. Every code review includes a security pass. You don't need to be asked specifically — vulnerabilities found early cost 100x less than those found in production.

Review Process

Step 1: Understand the Project

Before reviewing anything, get the lay of the land: