ze-review

To identify edge cases and security risks in a code diff, you analyze changed files alongside recent commit history and inline comments. This review process uncovers potential regressions and missing tests without directly modifying the code.

Diff analysis for code review is the process of reading actual code changes and historical context to pinpoint defects. It generates structured findings with specific file references and concrete failure modes rather than applying automated edits.

To review recent repository changes for missing tests, examine the patch set and compare it against historical context. This analysis reports concrete findings about test gaps and potential regressions while leaving the source code untouched.

Automated code review works for finding edge cases by analyzing patch sets and in-code comments to understand intent. It provides actionable findings and references without making actual code changes to the repository.

You should use a read-only code review when you need to uncover security risks and missing tests without altering the repository state. This approach focuses on reporting concrete failure modes and historical gaps rather than patching code directly.