Reproduce test failures and runtime errors to isolate root causes.
npx skills add https://github.com/abdias98/DevFlow --skill devflow-debug
Please help me install this Agent Skill. Skill: devflow-debug Source: https://github.com/abdias98/DevFlow/tree/main/.agents/skills/devflow-debugger Command: npx skills add https://github.com/abdias98/DevFlow --skill devflow-debug
Systematic debugger that performs root cause analysis on test failures, runtime errors, and reviewer findings. Never guesses — always reproduces, isolates, explains, and documents fixes.
Invoke the DevFlow Debugger with a failing test name or error message to start automated reproduction and root-cause analysis.
High-intent search queries and answers about installing and using this skill.
Root cause analysis on test failures and runtime errors requires deterministic reproduction to observe exact behavior, tracing data flow to isolate the cause, and explaining the rationale to generate actionable fixes. This process prevents guessing by relying on evidence-based explanations and thorough debug logging.
The best way to reproduce failures deterministically is to invoke the debugger with a specific failing test name or error message. This triggers automated reproduction and root-cause isolation, ensuring you observe exact behavior and gather evidence without relying on guesswork.
Document debugging sessions by capturing debug logs and memories during the root cause analysis process. This records the evidence-based explanations and actionable fixes, creating a reference to verify fixes and prevent future regressions.
Yes, automated debugging applies to reviewer findings in software projects using DevFlow. It handles reviewer findings by reproducing the reported issue deterministically, isolating the root cause through data flow tracing, and providing step-by-step fixes.
Test failure root cause analysis relies on guessing when it lacks deterministic reproduction and thorough debug logging. To stop guessing, you must reproduce failures to observe exact behavior, trace data flow dependencies, and generate evidence-based explanations for actionable fixes.
AndurilCodeDiagnose unexplained software failures through an evidence-first root-cause workflow.
JaimeJunrExecute unit and integration tests, analyze failures, and re-run to verify corrections.
stacksjsAnalyze proposed Stacks changes for scope, data flow, dependencies, and delivery artifacts.
DevattomDebug code errors through analysis, reproduction, solution proposal, and multi-layer verification.
