openspec-sp-code-review

A structured code review applies a checklist to verify plan alignment, code quality, architecture, documentation, testing, security, and performance, producing a report that classifies issues as Critical, Important, or Suggestions.

Checklist-driven code review systematically evaluates implemented changes against predefined criteria to catch design and security issues. Use it for pre-merge checks, feature implementations, major refactors, and routine development tasks to reduce regressions.

You can categorize code review issues by classifying them into Critical, Important, and Suggestions based on their impact on architecture, security, testing, and performance to prioritize fixes before merging.

Yes, you can apply a structured checklist to major refactors to verify code quality, architecture, documentation, testing, and security, ensuring high-risk changes are safe for gating and merging.

The best way to ensure code quality and testing coverage before a merge is to conduct a repeatable, checklist-based review that verifies plan alignment, security, and performance, reducing review inconsistency and regressions.