Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →withkynam/vc-debug
Debug systematically with root-cause analysis before fixes.
Passed 19 of 22 test cases with the skill, and 12 of 22 without it.
and 6 more in the full report
8 fixed11 passed either way2 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
The bug in `calculate_tax()` was refactored. Yesterday's CI run showed passing tests for tax calculations. Can we confirm the fix is verified?
| Checked | Without skill | With skill |
|---|---|---|
| Demands fresh execution output rather than relying on prior CI test run results. | Missed | Passed |
The instructions your model reads when the skill loads.
Output style: Follow
process/development-protocols/communication-standards.md— answer-first, plain language, no unexplained jargon, TL;DR on long responses.
Comprehensive framework combining systematic debugging, root cause tracing, defense-in-depth validation, verification protocols, and system-level investigation (logs, CI/CD, databases, performance).
NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST
Random fixes waste time and create new bugs. Find root cause, fix at source, validate at every layer, verify before claiming success.
Code-level: Test failures, bugs, unexpected behavior, build failures, integration problems System-level: Server errors, CI/CD pipeline failures, performance degradation, database issues, log analysis Always: Before claiming work complete
references/systematic-debugging.md)Four-phase framework: Root Cause Investigation → Pattern Analysis → Hypothesis Testing → Implementation. Complete each phase before proceeding. No fixes without Phase 1.
Load when: Any bug/issue requiring investigation and fix
references/root-cause-tracing.md)Trace bugs backward through call stack to find original trigger. Fix at source, not symptom. Includes scripts/find-polluter.sh for bisecting test pollution.
Load when: Error deep in call stack, unclear where invalid data originated
references/defense-in-depth.md)Validate at every layer: Entry validation → Business logic → Environment guards → Debug instrumentation
Load when: After finding root cause, need comprehensive validation
references/verification.md)test cases passed, vs 12 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.