Systematic debugging

Skill roronoazoroshao369/vibe-coding-os/skills/core/systematic-debugging

Vibe Coding OS — Claude/Codex/Cursor skill framework with 139 skills, 111 commands, 95 templates, 22 tracked sources, 28/28 validation gates PASS. Quality Shield, Engineering Discipline Pack, plugin marketplace.

Install

npx -y skills add roronoazoroshao369/vibe-coding-os --skill systematic-debugging

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.7 KB, 322 tokens by cl100k_base, as published. Nobody here has run it

Skill: Systematic Debugging

Purpose

Diagnose failures by forming hypotheses, collecting evidence, and changing one meaningful variable at a time.

When to use

Use for bugs, flaky tests, validation failures, unexpected agent output, or regressions where the cause is not obvious.

Inputs

Failure report, reproduction steps, logs or test output, recent changes, environment constraints, and suspected components.

Workflow

Reproduce or narrow the failure before proposing fixes when practical.
State observations separately from hypotheses.
Rank hypotheses by likelihood and cost to test.
Run the smallest experiment that can falsify the top hypothesis.
Change one meaningful variable at a time and record results.
After the fix, add or run a regression check and summarize the root cause at the right confidence level.

Outputs

A debugging log with reproduction status, hypotheses, experiments, root cause confidence, fix, and regression verification.

Failure modes

Jumping to a fix without reproducing or inspecting evidence.
Changing multiple variables so the result is uninterpretable.
Treating a workaround as root cause.
Failing to add or run a regression check.

Verification checklist

Reproduction or limitation is documented.
Hypotheses and observations are separated.
Experiments are small and evidence-based.
Fix is verified by targeted check or clear limitation.

Related mattpocock-inspired skill: skills/core/disciplined-diagnosis/SKILL.md for evidence-first bug diagnosis.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.