review

To perform an evidence-based code review, evaluate implementations against approved requirements by inspecting the effective diff, selecting evidence targets, validating findings, and reporting categorized conclusions with file paths and line numbers.

Spec compliance assessment verifies that implementations match approved behavior, constraints, scope, and proof requirements. It ensures code adheres to project standards by validating findings against concrete evidence rather than superficial approvals.

To classify review feedback, evaluate implementation feedback against project standards to categorize findings as must-fix, should-fix, nit, note, or needs-discussion. This structured approach prevents superficial approvals by prioritizing actionable items.

Validate implementation readiness by inspecting relevant changes, selecting appropriate review modes, validating findings, and synthesizing a defensible readiness decision. This checks code correctness, maintainability, security, and error-handling with concrete evidence.

Yes, plan validation prevents scope expansion by assessing implementation plans for feasibility and reporting categorized conclusions without expanding scope. It ensures reviews stay focused on approved requirements and project standards.

The best way to audit code quality is to inspect the effective diff, select distinct evidence targets, and validate findings supported by concrete evidence. This identifies correctness, maintainability, and structural issues while preventing superficial approvals.