jeremylongshore hyperflow-trace — root-cause phase (Antigravity single-agent)
Find the root cause before changing anything. Follow the hyperflow doctrine.
Steps
- Reproduce / locate. Read the error, stack trace, or failing test. Identify the exact failing line and the observed-vs-expected behavior.
- 5 Whys. Trace the causal chain backward — keep asking "why" until you reach the true cause, not a symptom.
- Hypotheses. List the 2-4 most plausible causes. For each, state a cheap test (read a file, add a log, run one test) that confirms or rules it out. Test them — narrow to the real cause.
- Confirm the root cause with evidence (a failing assertion, a value print, a reproduced path). Do not patch on a guess.
- Fix the root cause minimally. Add or update a test that would have caught it (characterization test before behavior change).
- Verify: re-run the failing case + the surrounding suite. Self-review the diff (L1-L3). Commit as
fix(<scope>): <root cause>(conventional, lowercase).
Rules
- Never blind-patch a symptom to make an error message disappear.
- No behavior change beyond the fix unless asked.
- If the root cause is unclear after hypothesis testing, surface what you found and what's still unknown — don't ship a speculative patch.
Source: jeremylongshore/claude-code-plugins-plus-skills → plugins/ai-agency/hyperflow/templates/antigravity/skills/hyperflow-trace/SKILL.md