code-review

To review a pull request with a risk-first mindset, provide the code diff or patch. The analysis prioritizes correctness, regressions, and missing test coverage, referencing exact file paths and line numbers to surface critical paths and potential side effects.

A risk-first code review approach evaluates code changes by prioritizing the detection of defects, regressions, and gaps in test coverage. It focuses analysis on risk-prone areas and critical paths to ensure correctness and prevent potential side effects in software projects.

Yes, automated code review can detect missing test coverage in commits. By analyzing provided diffs or patches, the review identifies gaps in coverage alongside correctness issues and potential regressions across software projects.

To analyze code diffs for regressions and side effects, submit the patch for review. The analysis applies a risk-first engineering mindset to identify defects, missing tests, and potential side effects, referencing exact file paths and line numbers when possible.

Yes, this code review workflow works with any software project's git diff. It requires no dependencies and can be integrated into existing development workflows to analyze pull requests and commits across various software projects.

You need a risk-first code review when integrating pull requests or commits into your development workflow and wanting to surface high-risk areas. It focuses on detecting correctness issues, regressions, and missing coverage before changes are merged.