hyperflow-trace
Hyperflow-trace is a debugging skill that systematically identifies root causes before applying fixes using a five-step methodology: reproducing the failure, tracing backward through causation, testing hypotheses, confirming the cause with evidence, and applying minimal fixes with tests. Use it when encountering bugs, test failures, runtime errors, build breaks, or unclear failures, especially when stack traces or error messages exist but the underlying problem remains obscured.
git clone --depth 1 https://github.com/jeremylongshore/claude-code-plugins-plus-skills /tmp/hyperflow-trace && cp -r /tmp/hyperflow-trace/plugins/ai-agency/hyperflow/templates/antigravity/skills/hyperflow-trace ~/.claude/skills/hyperflow-traceSKILL.md
# hyperflow-trace — root-cause phase (Antigravity single-agent) Find the root cause before changing anything. Follow the `hyperflow` doctrine. ## Steps 1. **Reproduce / locate.** Read the error, stack trace, or failing test. Identify the exact failing line and the observed-vs-expected behavior. 2. **5 Whys.** Trace the causal chain backward — keep asking "why" until you reach the true cause, not a symptom. 3. **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. 4. **Confirm** the root cause with evidence (a failing assertion, a value print, a reproduced path). Do not patch on a guess. 5. **Fix** the root cause minimally. Add or update a test that would have caught it (characterization test before behavior change). 6. **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.
Audit and fix Claude Code SKILL.md files to meet enterprise compliance standards. Analyzes frontmatter, required sections, and style. Use when you need to validate or repair skills in a plugin directory.
Learn how SKILL.md files work in Claude Code plugins, then build a production-quality agent skill from scratch. Covers frontmatter schema, body structure, testing, and iteration.
Step-by-step guide to writing a SKILL.md file for Claude Code. Learn how to plan, structure, and test auto-activating skills with proper frontmatter, allowed-tools, dynamic context injection, and supporting files.
|
|
|
|
|