systematic-debugging

A troubleshooting method that uses observed facts and testable explanations to find the cause of a software failure before changing code.

In plain words
What is it for?
Use it for reproducible bugs, crashes, failed checks, unexpected behavior, or inconsistent runtime states.
Why use it?
It helps separate confirmed causes from guesses and avoids applying fixes that only hide symptoms.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/sistema2d/framecode-vibework/systematic-debugging
Any agent
npx skills add Sistema2D/FrameCode-VibeWork --skill systematic-debugging
Clone the repo
git clone --depth 1 https://github.com/Sistema2D/FrameCode-VibeWork

Made for: Claude Code, Codex.

Per session 16 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 487 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00016 $0.00487
Opus 5 $0.00008 $0.00244
Sonnet 5 $0.00003 $0.00097
Haiku 4.5 $0.00002 $0.00049

Measured 2d ago against content hash 18b4a990ebbf, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

systematic-debugging scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

FCVW/skills/systematic-debugging/SKILL.md · 60 lines

How it starts

The opening of the file, as written. The whole thing — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Systematic debugging

Purpose

Find the smallest evidence-supported cause of a failure and distinguish diagnosis from implementation authorization.

Use conditions

Use for reproducible defects, crashes, failed checks, unexpected behavior, or inconsistent runtime state. For a question limited to diagnosis, do not apply a fix. For an authorized fix, follow the active plan and changelog contract.

Non-responsibilities

  • unrelated refactoring or speculative cleanup;
  • suppressing symptoms without explaining the cause;
  • publishing secrets, credentials, or unnecessary raw logs;
  • treating an unverified hypothesis as a finding.

Inputs

Expected behavior, observed behavior, environment, reproduction steps, logs or stack traces, recent changes, and the narrowest relevant source and test files.

Procedure

  1. Reproduce the problem or state why reproduction is currently impossible.
  2. Capture the exact symptom, environment, and smallest failing case.
  3. Form one ranked hypothesis tied to concrete evidence.
  4. Design a check that can disprove that hypothesis.
  5. Run the check and update the hypothesis from the result.
  6. Repeat until the cause is supported or the investigation is explicitly inconclusive.
  7. If a fix is authorized, add or identify a regression check, apply the minimal change, remove temporary instrumentation, and rerun affected validation.
  8. Promote durable incident learning to a troubleshooting record when recurrence, severity, or operational value justifies it.

Required output

Symptom, reproduction status, evidence, tested hypotheses, supported root cause or remaining uncertainty, affected scope, and validation results. If code changed, link the active plan and changelog entry.

Validation

The original failure is reproduced before the fix when feasible, the causal check changes as predicted, the regression check passes afterward, and unrelated validation has not regressed.

Exit criteria

Exit when the cause is supported and the authorized fix is validated, or when the remaining blocker and next evidence needed are recorded without presenting speculation as resolution.

Read the full file on GitHub · 60 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 60 lines · 16 tokens per session scan A 18b4a990ebbf

Subscribe to this mod's changes

systematic-debugging is a skill published in the GitHub repository Sistema2D/FrameCode-VibeWork (21 stars, last pushed 11d ago), licensed Apache-2.0. It adds 16 tokens to every session and 487 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.