Code Review and Quality

Purpose

Find defects and costly design regressions in a defined change. Preserve the useful five-axis review method of the existing skill while scaling the work to actual risk. A review verdict is not permission to merge, publish, or message others.

Modes

• Change review: review the named diff/PR/commit. If unspecified, inspect the local staged and unstaged changes plus relevant new files; state the baseline and scope.
• Maintainability: inspect the named files/functions for code smells. Read references/maintainability.md and its relevant language/examples guidance. Preserve behavior.
• Review and fix: when the user asks for repairs, implement clear in-scope fixes after diagnosis and verify them. An audit-only request remains read-only.

Workflow