Guide structured root-cause debugging with evidence collection and hypothesis testing.
npx skills add https://github.com/lleontor705/cortex-ia --skill debug-lleontor705
Please help me install this Agent Skill. Skill: debug Source: https://github.com/lleontor705/cortex-ia/tree/main/internal/assets/skills/debug Command: npx skills add https://github.com/lleontor705/cortex-ia --skill debug-lleontor705
Systematic root-cause debugging that identifies the true origin of bugs before proposing fixes, reducing wasted effort and regressions.
Initiate a debugging session following the Phase 1–3 workflow to locate the root cause and verify the fix.
High-intent search queries and answers about installing and using this skill.
Root-cause debugging identifies the true origin of bugs before proposing fixes, reducing wasted effort and regressions. It guides evidence collection, hypothesis testing, and targeted fixes through a structured investigation protocol.
Debugging multi-component systems and CI pipelines works best with a phase-based workflow that automates evidence collection, forms testable hypotheses, and validates fixes. It guides you to reproduce errors, gather artifacts, and trace data flow to the origin.
Systematic error investigation follows a phase-based workflow with explicit success criteria and guardrails. You reproduce errors, gather logs and artifacts, form explicit hypotheses, and trace data flow to isolate the origin before testing a single targeted fix.
Yes, structured root-cause debugging requires explicit hypotheses and single-change testing to validate fixes. It enforces a ReAct-style protocol that gathers logs and traces data flow, satisfying requirements for comprehensive investigation documentation.
A phase-based investigation workflow prevents wasted effort and regressions by locating the true origin of bugs before fixes. It separates investigation, diagnosis, and fix phases with explicit success criteria, ensuring targeted fixes are verified.
sQVeDiagnose bugs by tracing evidence and generating a BR issue template.
LEEI1337Identify root causes in technical issues before applying fixes.
michael-frelingDiagnoses CI pipeline build, lint, and test failures with iterative fixes and verification.
htlin222Search and analyze log files and codebases for error patterns and stack traces.
