review

To catch edge cases and logic bugs before merge, perform a full diff-based code review that analyzes risky inputs, missing error handling, and off-by-one mistakes across modified files. This semantic analysis detects failure paths that could break production behavior.

Verify code changes against project rules and memory context by applying a compliance check during your branch review. This uses recurring project lessons to sharpen the review and ensures modified files adhere to established repository conventions.

The best way to find unused code and debug output is garbage collection analysis across changed files. This cleanup process identifies commented-out fragments, leftover code, and debug statements before you merge the branch.

Yes, you can review branch changes for correctness and cleanup simultaneously through a four-phase code review. This process combines semantic analysis, edge case hunting, rules compliance, and garbage collection into a single comprehensive report.

Yes, semantic code analysis explains the blast radius of modified functions by detailing how changed methods and components alter behavior. This inspection highlights exactly where the impact of your branch changes reaches within the project.

You need a full diff-based inspection of your branch when you want to catch logic bugs, edge cases, rule violations, and leftover code before a merge. This review ensures code quality and correctness prior to integration.