systematic-debugging

Stars5

Forks0

UpdatedJune 1, 2026 at 21:28

Reproduce, isolate the root cause, fix the cause not the symptom, then prove it

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

New1Direction

New1Direction/korgex

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	systematic-debugging
description	Reproduce, isolate the root cause, fix the cause not the symptom, then prove it
version	1
trust	built-in

Resist the urge to guess-and-patch. A bug you can't reproduce isn't fixed.

Reproduce reliably. Find the smallest, deterministic way to trigger it. Capture the exact error/output. If you can't reproduce it, gather more signal before changing anything.
Locate it. Read the actual error and stack. Use Grep/Glob to find the code on the path; read the surrounding code and its callers. Form ONE hypothesis at a time about the root cause.
Test the hypothesis. Add a focused assertion, log, or a failing test that would be true only if your hypothesis holds. Confirm before fixing.
Fix the cause. Change the root cause, not the symptom. Avoid masking it with a catch-all or a retry. Keep the change minimal.
Prove it. Add a regression test that fails before your fix and passes after (see test-driven-development). Re-run the full suite; confirm nothing else broke.
State what the cause was and why the fix addresses it.

More from this repository

same repository

react-doctor

New1Direction/korgex

Catch bad React in your changes — run react-doctor's deterministic scan and fix what it flags

2026-06-055

security-scan

New1Direction/korgex

Run a verifiable security scan (vulns, secrets, misconfig) over code you wrote or deps you added, before calling the work done

2026-06-035

browser-automation

New1Direction/korgex

Drive a real browser verifiably — navigate, snapshot, act BY INDEX, extract; every step provable

2026-06-025

verifiable-orchestration

New1Direction/korgex

Run multi-agent work as ONE provable causal DAG — parallel subagents, an Orchestrate graph, an immutable spec-seed

2026-06-025

building-an-mcp-server

New1Direction/korgex

Author or connect a Model Context Protocol server so an agent gains new tools

2026-06-015

ci-cd-pipelines

New1Direction/korgex

Build automated pipelines that gate merges and ship reliably

2026-06-015

name	systematic-debugging
description	Reproduce, isolate the root cause, fix the cause not the symptom, then prove it
version	1
trust	built-in

Resist the urge to guess-and-patch. A bug you can't reproduce isn't fixed.

Reproduce reliably. Find the smallest, deterministic way to trigger it. Capture the exact error/output. If you can't reproduce it, gather more signal before changing anything.
Locate it. Read the actual error and stack. Use Grep/Glob to find the code on the path; read the surrounding code and its callers. Form ONE hypothesis at a time about the root cause.
Test the hypothesis. Add a focused assertion, log, or a failing test that would be true only if your hypothesis holds. Confirm before fixing.
Fix the cause. Change the root cause, not the symptom. Avoid masking it with a catch-all or a retry. Keep the change minimal.
Prove it. Add a regression test that fails before your fix and passes after (see test-driven-development). Re-run the full suite; confirm nothing else broke.
State what the cause was and why the fix addresses it.