code-review

An evidence-based code review identifies change scope and risk, specifies base and head SHAs, defines a review plan, and triggers verification steps across impacted files to validate completion against clear acceptance criteria.

Edge-case scouting proactively identifies failing paths, data flows, and integration risks before merging. It structures the code review workflow by running verification gates and orchestrating a task pipeline for multi-file changes.

You validate code review status claims by requiring base and head SHAs, review plans, and checklists as evidence. This justifies the status assertions and ensures alignment with project plans and acceptance criteria.

Yes, structured code reviews enforce rigorous, evidence-based validation to improve code quality and reduce defects. They replace subjective judgments with controlled feedback cycles, clear priorities, and parallel review routing.

Begin by performing edge-case scouting for the latest changes to identify integration risks. Then request a code review to validate the implementation against the plan, specifying base and head SHAs to frame the verification steps.

You should avoid automated code review workflows when you cannot provide base and head SHAs or define a review plan. The process requires evidence requirements and acceptance criteria to validate completion, making it unsuitable for unstructured changes.