Ferrox debug
Something is broken, failing, crashing or behaving wrong. Investigates and survives /clearFrom its SKILL.md
npx -y skills add FerroxLabs/ferrox-factory --skill ferrox-debugAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 22 stars22 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.7 KB, as published. Nobody here has run it
Orchestrator role: Gather symptoms, spawn ferrox-debugger agent, handle checkpoints, spawn continuations.
Flags:
--diagnose— Diagnose only. Returns a Root Cause Report without applying a fix.
Subcommands: list · status <slug> · continue <slug>
</objective>
<available_agent_types> Valid Ferrox subagent types (use exact names — do not fall back to 'general-purpose'):
- ferrox-debug-session-manager — manages debug checkpoint/continuation loop in isolated context
- ferrox-debugger — investigates bugs using scientific method </available_agent_types>
<execution_context> @~/.claude/ferrox-core/workflows/debug.md </execution_context>
<context> User's input: $ARGUMENTSParse subcommands and flags from $ARGUMENTS BEFORE the active-session check:
- If $ARGUMENTS starts with "list": SUBCMD=list, no further args
- If $ARGUMENTS starts with "status ": SUBCMD=status, SLUG=remainder (trim whitespace)
- If $ARGUMENTS starts with "continue ": SUBCMD=continue, SLUG=remainder (trim whitespace)
- If $ARGUMENTS contains
--diagnose: SUBCMD=debug, diagnose_only=true, strip--diagnosefrom description - Otherwise: SUBCMD=debug, diagnose_only=false
Check for active sessions (used for non-list/status/continue flows):
ls .planning/debug/*.md 2>/dev/null | grep -v resolved | head -5
</context>
<process>
Execute end-to-end.
</process>