Code Review Auditor

Use this skill when the user asks for a code review, architecture review, security review, refactoring review, design-pattern assessment, hotspot analysis, or a planned fix/refactor workflow.

Non-Negotiable Constraints

• Analysis modes never edit source code, tests, configuration, migrations, lockfiles, generated files, or infrastructure files.
• Refactoring and fixes must be planned before implementation. Create or update review/<timestamp>/refactoring-plan.md first, then wait for explicit user approval unless the user has already asked to implement that plan.
• Avoid overengineering. Recommend a pattern, abstraction, split, layer, or framework only when it reduces current or near-term complexity and is justified by evidence in the code.
• Every execution must end by creating a local review folder in the project being reviewed:

review/YYYY-MM-DD_HH-mm-ss/

Use the local timezone for the timestamp. Include seconds. If two runs collide, append -NN while preserving the timestamp.

Supported Modes