android-regression-diff-scan

Diff-guided analysis identifies suspect changes causing a regression between two git refs without a full build. It delegates the diff, logs, and metadata evaluation to a Sonnet sub-agent, ranking potential causes to avoid manual inspection of massive diffs and long rebuild times.

Analyzing a regression patch involves delegating diff analysis to a Sonnet sub-agent. It evaluates the regression bug brief and patch artifacts to rank suspect changes between two refs, handling large diffs efficiently by focusing on changed areas and relevant metadata.

Yes, diff-guided analysis supports branch-to-branch, release-to-release, and date-based baselines. It provides clear workflow guidance for these common regression scenarios, evaluating diffs and artifacts to surface suspect changes.

Yes, a regression bug brief and patch artifacts are required. The Sonnet sub-agent uses these inputs alongside the git diff to evaluate logs and suggestions, ultimately ranking the most suspect changes causing the regression.

Avoid traditional git bisect when builds are slow or diffs are large, making it impractical. In these cases, diff-guided analysis provides a faster alternative by delegating diff evaluation to a Sonnet sub-agent without requiring repeated builds.

Pre-flight checks ensure git references are reachable and history is intact. They also verify that patch artifacts are successfully generated for analysis, ensuring the Sonnet sub-agent has the necessary data to rank suspect changes.