implementation-review

Review a feature branch for cross-component bugs by analyzing the whole git diff to verify integration correctness, detect hidden regressions, and validate merge readiness across multiple modules before shipping.

Checking merge readiness involves validating boundary tests, error consistency, and success-criteria alignment across the completed implementation to ensure multiple tasks work together without integration gaps or documentation drift.

A standalone git diff review evaluates branch changes based solely on the code diff, while a plan-driven review compares the implementation against design context to catch implementation drift and verify cross-component correctness.

You need integration test validation for a feature branch when a multi-task backend change updates APIs, tests, and docs across several files, requiring verification that modules work together rather than in isolation before PR creation.

Yes, you can catch documentation drift and duplicated logic before creating a PR by running a holistic implementation review that checks error consistency and validates boundary tests across the completed feature branch.