.claude/skills/systematic-debuggingRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
These states come from the source or distribution context. None of the entries below are SkillVetAI compatibility test results.
These checks parse the fixed package against dated platform rules. They do not execute the Skill or verify task behavior.
.claude/skills/systematic-debuggingRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
.agents/skills/systematic-debuggingRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
skills/systematic-debuggingRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
This command is recorded from the source ecosystem and resolves the registry's latest release. The fixed release shown on this page should be inspected before adoption.
clawhub install @ivansslo/systematic-debuggingclawhub inspect @ivansslo/systematic-debugging --version 0.1.0This automated, non-executing scan is bound to this release hash. It is not a safety certification and may contain false positives or false negatives.
This is registry-supplied evidence for the recorded release, not an independent SkillVetAI scan. Check the canonical source for the full report, scanner versions, scope, and current moderation state.
The catalog stores hashes and an inventory summary for change detection. It does not republish the package contents.
sha256:b869ca742b726b6f33ceaa37d61ecc162c29621b614d34b8a5dcbced1014bef0skill-card.mdSKILL.mdInitial release of the systematic-debugging skill. - Introduces a structured, four-phase approach to debugging: root cause investigation, pattern analysis, hypothesis/testing, and implementation. - Emphasizes strict avoidance of fixes before root cause analysis; symptom-based fixes are considered failures. - Provides detailed steps and checklists for each debugging phase, including multi-component systems and data tracing. - Highlights red flags, common rationalizations, and signals that indicate deviation from systematic debugging. - Includes guidance for when repeated fixes fail, prompting architectural review.