jeremylongshore/tons-of-skills-marketplace / plugins/ai-agency/hyperflow/templates/antigravity/skills/hyperflow-trace
hyperflow-trace
VerifiedHyperflow debugging. Use for bugs, test failures, runtime errors, broken builds, or "this doesn't work" reports — verbs like debug, "fix it", solve, "why is X failing", "Y is broken", or a pasted stack trace. Systematic root-cause analysis before any patch — never blind-patch symptoms.
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.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |