.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 @eohmig/systematic-debuggingclawhub inspect @eohmig/systematic-debugging --version 1.0.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:1a322888225a47e0395bc58892a380484acca6bf30d0eb64fe0d61ec7690337ccondition-based-waiting-example.tscondition-based-waiting.mdCREATION-LOG.mddefense-in-depth.mdfind-polluter.shroot-cause-tracing.mdskill-card.mdSKILL.mdtest-academic.mdtest-pressure-1.mdtest-pressure-2.mdtest-pressure-3.mdsystematic-debugging 1.0.0 – Initial Release - Introduces a structured, four-phase debugging process focused on mandatory root cause investigation before attempting fixes. - Applies the process to any technical issue, with emphasis on traceability and data-driven evidence. - Enforces single-hypothesis testing and minimal changes per attempt. - Includes safeguards to prevent repeated unproductive fixes and mandates architectural review after multiple failures. - Lists common rationalizations and red flags to help maintain disciplined debugging practices.