Systematic Debugging
Use when a bug, flaky test, or runtime failure does not have an obvious root cause. This skill emphasizes reproduction, narrowing the search space, hypothesis testing, and evidence before proposing a fix.
Install
$ agentstack add skill-motao123-dev-workflow-kit-systematic-debugging ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-motao123-dev-workflow-kit-systematic-debugging) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Systematic Debugging
Use this skill when the problem is not yet understood well enough to fix safely.
Trigger Conditions
Use this skill when:
- a bug is intermittent or environment-specific
- a test fails without a clear reason
- symptoms are broad and the root cause is unknown
- multiple possible failure layers exist
- the user wants reproduction and diagnosis before implementation
Do not use this skill for obvious typo-level fixes or when the exact code change is already known.
Workflow
- Capture the observed failure and current evidence.
- Reproduce the issue or narrow why it cannot be reproduced.
- Reduce the search space by layer, component, or recent change.
- Form hypotheses and test them one by one.
- Separate symptoms from likely root cause.
- Recommend the smallest safe fix path.
Output
For non-trivial work, provide:
- observed behavior
- reproduction status
- narrowed scope
- hypotheses tested
- likely root cause
- recommended next step
Coordination
After diagnosis:
- move from diagnosis into the active implementation workflow for the actual fix
- use
fix-ciif the main failure surface is pipeline-only - use
browser-verificationwhen the bug is UI-visible
Invocation Examples
- "Use systematic-debugging to reproduce and narrow this flaky test failure."
- "Use systematic-debugging before changing code; I want the root cause first."
- "Use systematic-debugging to trace whether this is frontend, API, or database breakage."
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: motao123
- Source: motao123/dev-workflow-kit
- License: MIT
- Homepage: https://motao123.github.io/dev-workflow-kit/
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.