Opsmill Dev Test Driving Bugs
opsmill/infrahub
Writes a single failing test that reproduces a bug after its root-cause analysis is complete, before any fix is written.
A skill your agent uses when encountering any bug, test failure, or unexpected behavior.
Install Systematic Debugging
$ npx skills add tmdgusya/engineering-discipline --skill systematic-debugging -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install tmdgusya/engineering-discipline systematic-debugging --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/tmdgusya/engineering-discipline.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/systematic-debugging .claude/skills/systematic-debugging && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "systematic-debugging" agent skill from https://github.com/tmdgusya/engineering-discipline/tree/main/skills/systematic-debugging into .claude/skills/systematic-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "systematic-debugging", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/tmdgusya/engineering-discipline/tree/main/skills/systematic-debuggingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add tmdgusya/engineering-discipline --skill systematic-debugging -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install tmdgusya/engineering-discipline systematic-debugging --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tmdgusya/engineering-discipline.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/systematic-debugging .agents/skills/systematic-debugging && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "systematic-debugging" agent skill from https://github.com/tmdgusya/engineering-discipline/tree/main/skills/systematic-debugging into .agents/skills/systematic-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "systematic-debugging", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add tmdgusya/engineering-discipline --skill systematic-debugging -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install tmdgusya/engineering-discipline systematic-debugging --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tmdgusya/engineering-discipline.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/systematic-debugging .cursor/skills/systematic-debugging && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "systematic-debugging" agent skill from https://github.com/tmdgusya/engineering-discipline/tree/main/skills/systematic-debugging into .cursor/skills/systematic-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "systematic-debugging", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/tmdgusya/engineering-discipline.git --path skills/systematic-debugging--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add tmdgusya/engineering-discipline --skill systematic-debugging -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install tmdgusya/engineering-discipline systematic-debugging --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tmdgusya/engineering-discipline.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/systematic-debugging .gemini/skills/systematic-debugging && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "systematic-debugging" agent skill from https://github.com/tmdgusya/engineering-discipline/tree/main/skills/systematic-debugging into .gemini/skills/systematic-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "systematic-debugging", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install tmdgusya/engineering-discipline systematic-debuggingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add tmdgusya/engineering-discipline --skill systematic-debugging -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/tmdgusya/engineering-discipline.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/systematic-debugging .github/skills/systematic-debugging && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "systematic-debugging" agent skill from https://github.com/tmdgusya/engineering-discipline/tree/main/skills/systematic-debugging into .github/skills/systematic-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "systematic-debugging", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add tmdgusya/engineering-discipline --skill systematic-debugging -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install tmdgusya/engineering-discipline systematic-debugging --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tmdgusya/engineering-discipline.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/systematic-debugging .opencode/skills/systematic-debugging && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "systematic-debugging" agent skill from https://github.com/tmdgusya/engineering-discipline/tree/main/skills/systematic-debugging into .opencode/skills/systematic-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "systematic-debugging", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
systematic-debugging- GitHub stars
- 125
- Token cost
- ~2k tokens
- SKILL.md length
- 1,107 words
- Files
- 6
- Skills in repo
- 11
- Repo updated
- First seen
- Licence
- None found
At a glance
A skill your agent uses when encountering any bug, test failure, or unexpected behavior.
- Works in 10 steps: Define The Problem → Reproduce Or Instrument → Gather Evidence → …
- Encountering any bug
- SKILL.md covers Hard Gates, When To Use, Required Output Contract and Workflow, plus 4 more sections
- Runs TypeScript and Shell scripts from its folder
What it does
Systematic Debugging is an agent skill from tmdgusya/engineering-discipline. Use when encountering any bug, test failure, or unexpected behavior. Enforces a strict reproduce-first, root-cause-first, failing-test-first debugging workflow before fixing.
Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files (for example `condition-based-waiting-example.ts`, `condition-based-waiting.md` and `defense-in-depth.md`).
It sits in Development, covering Debugging, Failing and flaky tests and Root cause analysis. The repository describes itself as: SKILL for engineering-discipline.
When your agent uses it
- Encountering any bug
- Unexpected behavior
Example prompts
- “/systematic-debugging”
Requirements
- Node.js
- A Bash shell
Workflow steps
10 steps, taken from the step headings in SKILL.md.
- Define The Problem
- Reproduce Or Instrument
- Gather Evidence
- Isolate Root Cause
- Lock The Failure
- Implement A Single Fix
- Verify And Close
- Reproduction Failed
- Three Failed Fixes
- No Failing Guard
What it can do on your machine
Read from SKILL.md and the folder at commit 137dead. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships script files (TypeScript and Shell), which the agent can run.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Systematic Debugging loads about 2k tokens when it runs. Until then it costs about 49 tokens; SKILL.md has 1,107 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Without a licence we can't republish the file, so here is its outline and opening line. It has 1,107 words (~1,982 tokens).
“A strict debugging workflow. Use when dealing with bugs, test failures, or unexpected behavior.”
- name
- systematic-debugging
Files
SKILL.md and 5 other files in skills/systematic-debugging of tmdgusya/engineering-discipline.
- SKILL.md
- condition-based-waiting-example.ts
- condition-based-waiting.md
- defense-in-depth.md
- find-polluter.sh
- root-cause-tracing.md
Open the folder on GitHubat commit 137dead
Compare with similar skills
Systematic Debugging next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Systematic Debugging this skilltmdgusya/engineering-discipline | 125 | — | ~2k | Automated safety check: Pass | None | |
| Opsmill Dev Test Driving Bugsopsmill/infrahub | 529 | — | ~4k | Automated safety check: Pass | Apache-2.0 | |
| Systematic Debuggingforyourhealth111-pixel/Vibe-Skills | 3.6k | — | ~2.6k | Automated safety check: Pass | Apache-2.0 | |
| Systematic DebuggingChrisWiles/claude-code-showcase | 6.1k | 3 repos | ~1.2k | Automated safety check: Pass | None | |
| Debugging and Error Recoveryaddyosmani/agent-skills | 102k | 1 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Systematic Debugginged3dai/ed3d-plugins | 250 | 3 repos | ~2.4k | Automated safety check: Pass | None |
Similar skills
Systematic Debugging
foryourhealth111-pixel/Vibe-Skills
Root-cause route for actual bugs, failing tests, build errors, crashes, stack traces, and unexpected behavior.
Systematic Debugging
ChrisWiles/claude-code-showcase
Applies a four-phase debugging routine that finds the root cause of a bug or failing test before any fix is written.
Debugging and Error Recovery
addyosmani/agent-skills
Applies a stop-the-line rule and a step-by-step triage when tests fail, builds break or something stops working, aiming at the root cause instead of guesses.
Systematic Debugging
ed3dai/ed3d-plugins
A skill your agent uses when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework (root cause investigation, pattern analysis, hypothesis…
Debugging And Error Recovery
abashev/vfs-s3
Guides systematic root-cause debugging. An agent skill from abashev/vfs-s3.
More from tmdgusya/engineering-discipline
All 11 skills in this repoClarification
tmdgusya/engineering-discipline
A skill your agent uses when a user's request is vague, ambiguous, or underspecified.
Clean AI Slop
tmdgusya/engineering-discipline
Corrective cleanup of AI-generated code — removes LLM-specific patterns while preserving behavior.
Karpathy
tmdgusya/engineering-discipline
Behavioral guardrails to prevent common LLM coding mistakes — enforces surgical changes, assumption verification, and scope discipline before and during implementation.
Plan Crafting
tmdgusya/engineering-discipline
A skill your agent uses when a task's scope is clear and multi-step implementation is needed, before touching code.
Review Work
tmdgusya/engineering-discipline
Use after run-plan completes to independently verify the implementation.
Run Plan
tmdgusya/engineering-discipline
A skill your agent uses when you have a written implementation plan to execute.
Related
Categories
Questions about Systematic Debugging
What does Systematic Debugging do?
A skill your agent uses when encountering any bug, test failure, or unexpected behavior. Systematic Debugging is an agent skill from tmdgusya/engineering-discipline. Use when encountering any bug, test failure, or unexpected behavior.
When should I use Systematic Debugging?
Systematic Debugging fits situations like: encountering any bug; unexpected behavior.
How do I install Systematic Debugging in Claude Code?
Run `npx skills add tmdgusya/engineering-discipline --skill systematic-debugging -a claude-code`. Or copy the skill folder (skills/systematic-debugging in tmdgusya/engineering-discipline) into .claude/skills/systematic-debugging in your project. Claude Code loads it when a task matches its description.
How do I install Systematic Debugging in Codex?
Run `npx skills add tmdgusya/engineering-discipline --skill systematic-debugging -a codex`. Or copy the skill folder (skills/systematic-debugging in tmdgusya/engineering-discipline) into .agents/skills/systematic-debugging in your project. Codex loads it when a task matches its description.
Can I use Systematic Debugging in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add tmdgusya/engineering-discipline --skill systematic-debugging -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/systematic-debugging, .gemini/skills/systematic-debugging, .github/skills/systematic-debugging and .opencode/skills/systematic-debugging in your project.
What does Systematic Debugging need to run?
Going by SKILL.md and its folder, Systematic Debugging needs TypeScript and a shell for the scripts in its folder. Our summary lists: Node.js; A Bash shell.
Does Systematic Debugging access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Systematic Debugging safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Systematic Debugging use?
No licence was found for Systematic Debugging or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Systematic Debugging use?
About 2k tokens (SKILL.md is roughly 7.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Systematic Debugging?
Skills that share tags, products or a category with Systematic Debugging: Opsmill Dev Test Driving Bugs (opsmill/infrahub, 529 stars), Systematic Debugging (foryourhealth111-pixel/Vibe-Skills, 3.6k stars), Systematic Debugging (ChrisWiles/claude-code-showcase, 6.1k stars) and Debugging and Error Recovery (addyosmani/agent-skills, 102k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Systematic Debugging?
tmdgusya (a GitHub user) maintains it in tmdgusya/engineering-discipline, which has 125 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on July 3, 2026.
Source: tmdgusya/engineering-discipline on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.