Pester Failure Analysis
PowerShell/PowerShell
Investigates failing Pester tests in PowerShell CI jobs by following a six-step workflow from pull request status to documented fix recommendations.
A skill your agent uses when investigating a bug, test failure, flaky test, unexpected behavior, or a hotfix, or an unexplained or failed fix; find the root cause first.
Install Systematic Debugging
$ npx skills add KbWen/agentic-os --skill systematic-debugging -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install KbWen/agentic-os 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/KbWen/agentic-os.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/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/KbWen/agentic-os/tree/main/.agents/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/KbWen/agentic-os/tree/main/.agents/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 KbWen/agentic-os --skill systematic-debugging -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install KbWen/agentic-os systematic-debugging --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/KbWen/agentic-os.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/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/KbWen/agentic-os/tree/main/.agents/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 KbWen/agentic-os --skill systematic-debugging -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install KbWen/agentic-os systematic-debugging --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/KbWen/agentic-os.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/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/KbWen/agentic-os/tree/main/.agents/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/KbWen/agentic-os.git --path .agents/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 KbWen/agentic-os --skill systematic-debugging -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install KbWen/agentic-os systematic-debugging --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/KbWen/agentic-os.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/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/KbWen/agentic-os/tree/main/.agents/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 KbWen/agentic-os 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 KbWen/agentic-os --skill systematic-debugging -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/KbWen/agentic-os.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/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/KbWen/agentic-os/tree/main/.agents/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 KbWen/agentic-os --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 KbWen/agentic-os systematic-debugging --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/KbWen/agentic-os.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/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/KbWen/agentic-os/tree/main/.agents/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
- 206
- Token cost
- ~496 tokens
- SKILL.md length
- 239 words
- Files
- 2
- Skills in repo
- 12
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when investigating a bug, test failure, flaky test, unexpected behavior, or a hotfix, or an unexplained or failed fix; find the root cause first.
- Works in 4 steps: Observe → Hypothesize → Verify → …
- Investigating a bug
- SKILL.md covers Overview, Ironclad Rules, When to Use and Four-Phase Process, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Systematic Debugging is an agent skill from KbWen/agentic-os. Use when investigating a bug, test failure, flaky test, unexpected behavior, or a hotfix, or an unexplained or failed fix; find the root cause first.
Its SKILL.md is about 500 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).
It sits in Testing & QA, covering Failing and flaky tests, Debugging and Root cause analysis. The repository describes itself as: Governance framework for AI coding agents. It runs them through a five-step workflow (plan, build, review, test, ship) where no step counts as done without evidence. Drop-in… The licence is MIT.
When your agent uses it
- Investigating a bug
- Unexpected behavior
- Find the root cause first
Example prompts
- “/systematic-debugging”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 81a4034. 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
No scripts in the folder and no shell commands in SKILL.md.
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 496 tokens when it runs. Until then it costs about 43 tokens; SKILL.md has 239 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
The full file from KbWen/agentic-os at commit 81a4034, republished under its MIT licence (© KbWen). 239 words, ~496 tokens.
Download SKILL.mdSave it as
.claude/skills/systematic-debugging/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- systematic-debugging
- description
- Use when investigating a bug, test failure, flaky test, unexpected behavior, or a hotfix, or an unexplained or failed fix; find the root cause first.
Systematic Debugging
Overview
The core of systematic debugging is: understand first, then fix. When encountering a bug, clarify symptoms, reproduction conditions, and blast radius. Draw hypotheses, verify them with experiments to isolate the root cause, and only then submit a minimal, verifiable fix.
Ironclad Rules
- No random patching: Do not submit fixes without root cause evidence.
- Change one variable at a time: Prevent unexplainable results from touching multiple areas at once.
- Fixes MUST include evidence: Include reproduction steps, verification, and regression results.
When to Use
- Hotfix incident response.
- Flaky tests.
- Cross-module anomalies that aren't intuitively obvious.
- Any "fixed but I don't know why" risk scenarios.
Four-Phase Process
Phase 1: Observe
- Precisely record error messages, timestamps, and input conditions.
- Create a Minimal Reproducible Example (MRE).
- Mark the blast radius (affected modules/users).
Phase 2: Hypothesize
- Propose 1–3 testable root cause hypotheses.
- Design "falsifiable" checks for each hypothesis.
- Prioritize high-probability, low-cost verifiable items.
Phase 3: Verify
- Run experiments and retain output logs.
- Adjust only one variable to confirm causality.
- Remove falsified hypotheses to converge on the most likely root cause.
Phase 4: Fix
- Implement a Minimal Fix.
- Add a Regression Test.
- Verify: The original error disappears AND existing behavior is not broken.
Common Mistakes
- Modifying code before reproducing the issue.
- Modifying too many files at once, failing to locate the effective fix point.
- Treating "accidental passes" as root cause resolved.
- Lacking regression tests, causing similar issues to happen again.
© KbWen, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in .agents/skills/systematic-debugging of KbWen/agentic-os.
- SKILL.md
- agents/openai.yaml
Open the folder on GitHubat commit 81a4034
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 skillKbWen/agentic-os | 206 | — | ~496 | Automated safety check: Pass | MIT | |
| Pester Failure AnalysisPowerShell/PowerShell | 56k | — | ~5.1k | Automated safety check: Pass | MIT | |
| Map Debugazalio/map-framework | 156 | — | ~4.6k | Automated safety check: Pass | MIT | |
| Map Debugazalio/map-framework | 156 | — | ~4.6k | Automated safety check: Pass | MIT | |
| Opsmill Dev Test Driving Bugsopsmill/infrahub | 531 | — | ~4k | Automated safety check: Pass | Apache-2.0 | |
| Systematic Debuggingforyourhealth111-pixel/Vibe-Skills | 3.6k | — | ~2.6k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Map Debug
azalio/map-framework
Structured MAP debugging via decomposer, actor, and monitor agents.
Map Debug
azalio/map-framework
Structured MAP debugging via task-decomposer, actor, and monitor agents.
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.
Systematic Debugging
foryourhealth111-pixel/Vibe-Skills
Root-cause route for actual bugs, failing tests, build errors, crashes, stack traces, and unexpected behavior.
Regression Root Cause Analyzer
ArabelaTso/Skills-4-SE
Locate root causes of failing regression tests by analyzing code changes, error messages, and test dependencies.
More from KbWen/agentic-os
All 12 skills in this repoAPI Design
KbWen/agentic-os
Design or review REST/GraphQL APIs when endpoints or contracts change.
Frontend Patterns
KbWen/agentic-os
Apply frontend conventions when components, pages, forms, or client state change.
Karpathy Principles
KbWen/agentic-os
Behavioral guidelines to reduce common LLM coding mistakes — Think Before Coding, Simplicity First, Surgical Changes, Goal-Driven Execution.
Production Readiness
KbWen/agentic-os
Use at review and ship, automatically for feature or architecture changes and on request for error handling, logging, crash reporting, or observability; verify errors reach production monitoring.
Doc Lookup
KbWen/agentic-os
Check official docs when framework APIs or configuration may be version-sensitive.
Database Design
KbWen/agentic-os
Design schemas and migrations when persistent data structures change.
Related
Categories
Questions about Systematic Debugging
What does Systematic Debugging do?
A skill your agent uses when investigating a bug, test failure, flaky test, unexpected behavior, or a hotfix, or an unexplained or failed fix; find the root cause first. Systematic Debugging is an agent skill from KbWen/agentic-os. Use when investigating a bug, test failure, flaky test, unexpected behavior, or a hotfix, or an unexplained or failed fix; find the root cause first.
When should I use Systematic Debugging?
Systematic Debugging fits situations like: investigating a bug; unexpected behavior; find the root cause first.
How do I install Systematic Debugging in Claude Code?
Run `npx skills add KbWen/agentic-os --skill systematic-debugging -a claude-code`. Or copy the skill folder (.agents/skills/systematic-debugging in KbWen/agentic-os) 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 KbWen/agentic-os --skill systematic-debugging -a codex`. Or copy the skill folder (.agents/skills/systematic-debugging in KbWen/agentic-os) 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 KbWen/agentic-os --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?
SKILL.md names no scripts, command-line tools or credentials: Systematic Debugging is instructions for the agent only.
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?
Systematic Debugging is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Systematic Debugging use?
About 496 tokens (SKILL.md is roughly 2k 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: Pester Failure Analysis (PowerShell/PowerShell, 56k stars), Map Debug (azalio/map-framework, 156 stars), Map Debug (azalio/map-framework, 156 stars) and Opsmill Dev Test Driving Bugs (opsmill/infrahub, 531 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Systematic Debugging?
KbWen (a GitHub user) maintains it in KbWen/agentic-os, which has 206 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on October 6, 2026.
Source: KbWen/agentic-os on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.