hyperflow-trace
Hyperflow 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.
Allowed Tools
No tools specified
Provided by Plugin
hyperflow
Point it at a GitHub issue and get back a reviewed pull request. Hyperflow turns one AI coding session into a structured engineering pipeline: plan sharpens and decomposes the work, dispatch fans out parallel workers, and a domain specialist reviews every step — nothing ships unreviewed. 18 skills, 22 specialist reviewer and investigator agents, adaptive depth so a 5-line fix never triggers a deep run, and persistent per-project memory that lives in your repo and never leaves it. Runs on whatever model your session already uses — zero config, no API keys, no daemon. Works across Claude Code, Codex App/CLI, OpenCode, Grok, Antigravity, and Cursor.
Installation
This skill is included in the hyperflow plugin:
/plugin install hyperflow@claude-code-plugins-plusClick to copy
Instructions
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((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.