code-review

To review code diffs before a pull request, inspect implementation changes and classify findings by severity. This process evaluates requirements alignment, error handling, and dead code to identify critical defects while they are cheap to fix.

A pre-PR quality gate review is a structured diff analysis that validates test coverage, dependency direction, and naming conventions. It categorizes findings as Critical, Important, or Minor to ensure spec compliance before merging code.

Validating test coverage and side effects during diff inspection requires comparing changes against specs and checking responsibility boundaries. This catches non-blocking issues and ensures error handling aligns with software engineering requirements.

Yes, applying code review to follow-up responses validates subsequent implementation diffs. It performs a final sanity check on dependency direction and dead code before merging, ensuring all review-blocking issues are resolved.

The best way to classify code review findings is through structured severity ranking, sorting issues into Critical, Important, or Minor categories. This ensures blocking defects are distinguished from minor naming or dead code issues.

A final merge check for dead code and dependency direction is needed whenever you want a sanity check before merging. It validates implementation diffs and ensures no non-blocking findings or spec mismatches remain.