trace
FeaturedUse when encountering bugs, test failures, runtime errors, broken builds, or "this doesn't work" reports. Systematic root-cause analysis before any patch — never blind-patches symptoms. Standalone, ends with a final-integration review of the fix. Trigger with /hyperflow:trace, "debug this", "find the root cause", "why is this failing", "this test is broken".
Install
Quality Score: 99/100
Skill Content
Details
- Author
- jeremylongshore
- Repository
- jeremylongshore/claude-code-plugins-plus-skills
- Created
- 11 months ago
- Last Updated
- today
- Language
- Python
- License
- MIT
Integrates with
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
trace
Use when diagnosing or fixing a bug, regression, failing test, or unexplained behavior by establishing root cause before editing.
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.
tracing-root-causes
Owns debugging end to end — reproduce, isolate, hypothesize, disconfirm, fix — with competing hypotheses, evidence ranked by strength, active disconfirmation, and a fix at the source rather than the symptom. Use for any bug, test failure, crash, regression, flaky or intermittent failure, performance problem, build failure, or unexpected behavior, BEFORE proposing or applying a fix; and for explaining why something happened (production incidents, surprising benchmark results) when no fix is on the table yet. Especially when an "obvious culprit" is tempting, when a previous fix did not work, or when time pressure makes guessing attractive. Supersedes superpowers:systematic-debugging as the house debugging skill.