android-regression-diff-scan

Analyzes the diff between two git refs to identify likely regression causes.

7|Updated Apr 15, 2026

Search Tags:#git #debugging #regression #android #bisect #sonnet #diff-scan

Ready to run

npx skills add https://github.com/himattm/skills --skill android-regression-diff-scan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: android-regression-diff-scan
Source: https://github.com/himattm/skills/tree/main/plugins/android/skills/android-regression-diff-scan
Command: npx skills add https://github.com/himattm/skills --skill android-regression-diff-scan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify regression causes between two git refs by delegating diff analysis to a Sonnet sub-agent, avoiding manual inspection of massive diffs and long wait times for builds.

Core Features & Use Cases

Delegated diff analysis surfaces suspect changes without requiring a full rebuild.
Efficient handling of large diffs by focusing on changed areas and relevant metadata.
Clear workflow guidance for common regression scenarios (release-to-release, branch-to-branch, or date-based baselines).
Pre-flight checks to ensure references are reachable, history is intact, and patch artifacts are generated for analysis.

Quick Start

Identify good and bad refs, generate a regression patch, and delegate the analysis to a Sonnet sub-agent.

Frequently Asked Questions about android-regression-diff-scan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I find a regression in a large Android git diff without waiting for a full build?▼

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.

What is the best way to analyze a regression patch between two git refs?▼

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.

Can I use diff-guided analysis for branch-to-branch or release-to-release Android regressions?▼

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.

Do I need a regression bug brief to identify suspect changes with a Sonnet sub-agent?▼

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.

When should I avoid traditional git bisect for finding an Android 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.

What pre-flight checks are needed before delegating a git diff analysis?▼

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.