convergence-review

You can review a git diff against the base branch by loading the diff output and running a two-stage evaluation that first verifies correctness against the design outline, then assesses architecture, security, data safety, tests, and pattern consistency.

A two-stage code review first verifies that code changes accurately implement designed decisions and complete all outline stages, then evaluates code quality across architecture, security, data safety, tests, and pattern consistency to guide merges.

You verify code correctness against a design outline by comparing the actual git diff against the base branch to confirm all designed decisions are implemented, outline stages are complete, and any missing or extra requirements are identified.

You can assess architecture and security quality from a git diff by evaluating the changes against the base branch to compile actionable findings regarding data safety, code quality, tests, and pattern consistency for merge evaluation.

You need to perform a rigorous code review of your diffs after implementing a feature or evaluating a PR to ensure implementation accuracy and code quality before merging into the base branch.

Evaluating code quality and correctness before a merge requires access to the git diff against the base branch, the design outline, and relevant tests to accurately assess implementation and quality across multiple dimensions.