code-review

Code review evaluates pull requests and committed changes against canonical patterns to surface architecture drift and priority issues fast. It provides phase-driven evaluation across consistency, error handling, security, and performance to guide concrete refactors.

The best way to enforce code quality baselines is to apply canonical review patterns to your feature branch diff. This compares changed files against at-a-glance baselines to identify inconsistencies and guides documentation updates aligned with codebase conventions.

Yes, you can review UI components, API routes, and CLI commands for state and data flow issues. The review process applies phase-driven evaluation to surface priority issues and guide concrete fixes across these changed code paths.

Code review surfaces priority issues by evaluating pull request diffs across multiple dimensions including types, contracts, complexity, and readability. It compares changes against baselines and canonical patterns to highlight the top issues that matter.

You need to check code for security and error handling consistency during pull request reviews and after feature work. This phase-driven evaluation identifies drift from canonical patterns and guides concrete refactors to maintain codebase conventions.

Code review works with both committed changes and open pull requests. It evaluates feature branches and committed code across API routes, CLI commands, and UI components to surface architecture drift and pattern inconsistencies.