Strict Code Review

Use this skill for a strict review focused on implementation quality, maintainability, abstraction quality, and codebase health.

Default posture: findings first and read-only. Edit files or mutate PR state only when the user explicitly asks for that follow-up.

Default scope is the current PR diff or current branch diff, including related uncommitted local changes. If the user gives an explicit scope, use that instead: a PR URL, pasted diff, file, package, module, component, plan, or current conversation direction.

For stacked branches, do not default to main...HEAD when that would include parent-branch work. Resolve the PR base/head, dependency branch, or explicit commit range first. Prefer the PR's actual changed commits, HEAD^..HEAD, or the user-provided range when the task is to review only the top stack item.

Core Standard

Rethink how to structure or implement the change to meaningfully improve code quality without changing behavior.

Look for "code judo" moves: restructurings that preserve behavior while making the implementation dramatically simpler, smaller, more direct, and more inevitable in hindsight.

Do not stop at local cleanup when a clearer framing could delete whole branches, helpers, modes, conditionals, wrappers, layers, or concepts.

Workflow