code-review-checklist

Independent code review verification requires separating reviewer analysis from developer self-checks to validate critical claims. This process applies governance rules to modified files, producing structured review artifacts with explicit verification evidence.

A BR-002 compliant code review report is a structured artifact documenting independent verification of changed files. It includes severity-based issue classification, reviewer verification details, and explicit documentation of review coverage and assumptions.

Classify code review findings by severity using BR-004 compliant categories: blocker, major, minor, and note. This governance alignment ensures changes stay within defined role boundaries and workflows while providing auditable feedback.

Yes, applying an independent reviewer workflow as a quality gate prevents self-check biases. It mandates separate reviewer analysis to validate developer claims, ensuring governance alignment and comprehensive documentation synchronization across modified files.

Governance rule application requires a defined set of modified files to process. Reviewers must explicitly document assumptions and review coverage, meaning incomplete file definitions or undocumented workflows can limit the thoroughness of the final review artifact.