code-review

Reviewing a git diff for security risks involves systematically analyzing file-level changes to catch bugs, state issues, and missing tests. This process prioritizes severity-ordered findings, citing specific file locations to ensure evidence-backed inspection before merging.

Yes, you can check missing test coverage in a GitHub pull request by applying a consistent diff review workflow. It flags validation gaps and behavior changes, ensuring that open pull requests are inspected for missing tests alongside security and regression risks.

The best way to analyze code changes for migration issues is through evidence-first diff inspection. This approach targets risky coupling, data migration problems, and secret handling mistakes, producing structured findings ordered by severity to highlight critical risks.

Code review works for both local branch changes and open GitHub pull requests. It applies a consistent workflow across refactors, behavior updates, and migrations, delivering severity-ordered findings and open questions regardless of the source.

To identify risky side effects and coupling in a code refactor, inspect the change set for behavior changes and validation gaps. The review process flags risky couplings and side effects, recommending targeted repo-native checks to verify engineering quality.

A structured code review output should include severity-ordered findings, open questions, and a brief summary to satisfy engineering quality requirements. It must cite specific files and locations, prioritizing the most serious risks first based on evidence from tests and linting.