test-first
Use before implementing a feature or bugfix — write the failing test before the code.
Use when you hit a bug, test failure, or unexpected behavior — find the root cause before changing code.
$ npx -y skills add Kilbex/Vigla --skill systematic-debugging --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/systematic-debuggingContext preview
The summary Claude sees to decide when to auto-load this skill.
Use when you hit a bug, test failure, or unexpected behavior — find the root cause before changing code.
name: Systematic debugging description: Use when you hit a bug, test failure, or unexpected behavior — find the root cause before changing code. scope: repo enabled: true priority: 90
When something is broken:
1. Reproduce it with the smallest possible input, ideally a failing test. 2. Read the actual error and the surrounding code before forming a theory. 3. Form ONE hypothesis, find the cheapest observation that would confirm or kill it, and check. 4. Fix the root cause, not the symptom. If you cannot explain *why* it broke, you are not done. 5. Re-run the reproduction to confirm the fix, then run the wider suite for regressions.
Open-source mission control for coding agents. Run cross-vendor workers in isolated worktrees, audit every submission, and revert an entire mission.
Use before implementing a feature or bugfix — write the failing test before the code.
Use before claiming work is complete — prove it with commands, do not assume.