systematic-debugging
Debug Root Causes Systematically
Repeated fix attempts waste time and often hide the real cause of bugs. This skill guides Claude, Codex, and Claude Code through evidence-first debugging.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "systematic-debugging" from https://skillstore.io/skills/codingcossack-systematic-debugging.md and its manifest at https://skillstore.io/api/skills/codingcossack-systematic-debugging/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "systematic-debugging". A test fails only in CI after a recent dependency update.
Expected outcome:
- Confirm the exact error and CI reproduction path.
- Compare local and CI environment differences.
- Form one hypothesis about the dependency change.
- Run one focused verification before changing code.
Using "systematic-debugging". An asynchronous test uses fixed waits and fails randomly.
Expected outcome:
- Identify the actual condition the test needs.
- Replace sleep timing with condition-based waiting.
- Keep a timeout with a clear failure message.
- Document any remaining real timing requirement.
Using "systematic-debugging". A project unexpectedly creates files in the source directory.
Expected outcome:
- Trace the filesystem operation backward through callers.
- Find the first invalid path or empty value.
- Fix the source of the bad value.
- Add validation at boundaries to prevent recurrence.
Security Audit
Medium RiskMost static findings are false positives caused by Markdown fences, TypeScript template literals, comments, and benign local examples. One medium contextual issue remains: the guidance can encourage environment values to be logged during debugging.
Confirmed security concerns (1)
Risk Factors
⚙️ External commands (24)
📁 Filesystem access (2)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/codingcossack-systematic-debugging/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/codingcossack-systematic-debugging?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/codingcossack-systematic-debugging?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/codingcossack-systematic-debugging/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/codingcossack-systematic-debugging.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
CodingCossack. (2026). systematic-debugging security audit report (audit version 8) [Author version unspecified]. Skillstore. https://skillstore.io/skills/codingcossack-systematic-debugging/audits/8BibTeX citation
@techreport{codingcossack-codingcossack-systematic-debugging-2026,
author = {CodingCossack},
title = {systematic-debugging security audit report (audit version 8)},
institution = {Skillstore},
year = {2026},
number = {8},
url = {https://skillstore.io/skills/codingcossack-systematic-debugging/audits/8},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "systematic-debugging security audit report (audit version 8)"
version: "unspecified"
type: report
authors:
- name: "CodingCossack"
date-released: "2026-07-05"
url: "https://skillstore.io/skills/codingcossack-systematic-debugging/audits/8"
identifiers:
- type: other
value: "skillstore:codingcossack-systematic-debugging:audit:8"
description: "Skillstore immutable audit report identifier"
Compare variants
12 installable variantsEach author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.
Why this variant is first
asmayaseen-systematic-debugging
2026-08-21
chriswiles-systematic-debugging
2026-08-21
doyajin174-systematic-debugging
2026-08-21
dmjgilbert-systematic-debugging
2026-08-21
codingcossack-systematic-debugging
2026-08-21
zhanlincui-systematic-debugging
2026-08-21
obra-systematic-debugging
2026-08-21
cycleaddict-systematic-debugging
2026-08-21
davila7-systematic-debugging
2026-08-21
dyai2025-systematic-debugging
2026-08-21
cygnusfear-systematic-debugging
2026-08-21
sickn33-systematic-debugging
2026-08-21
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Diagnose Failing Tests
Trace a recurring test failure from symptom to source before changing production code.
Stabilize Async Workflows
Replace arbitrary sleeps with waits for observable conditions and clear timeout errors.
Review Repeated Fix Attempts
Pause after several failed changes, inspect assumptions, and decide whether architecture is the root issue.
Try These Prompts
Use systematic-debugging for this issue. Ask for the error, reproduction steps, recent changes, and attempted fixes before proposing a solution.
Apply root cause tracing to this failing test. Identify the symptom, immediate cause, caller chain, original trigger, and smallest verification step.
Design diagnostic instrumentation for this failing workflow. Show what evidence to collect at each boundary and how each result changes the hypothesis.
I have tried three fixes for this bug. Use the escalation process to question assumptions and propose a verification plan before another change.
Best Practices
- Gather evidence before proposing a fix.
- Change one variable per hypothesis test.
- Create a failing test before implementing the fix.
Avoid
- Applying a quick fix before tracing the root cause.
- Stacking several changes into one debugging attempt.
- Ignoring repeated failed fixes instead of escalating assumptions.
Frequently Asked Questions
What problem does this skill solve?
Does it run commands automatically?
Can it help with flaky tests?
When should I use escalation?
Is it specific to TypeScript?
How should secrets be handled during debugging?
Developer Details
Author
CodingCossackLicense
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Repository
https://github.com/CodingCossack/agent-skills-library/tree/main/skills/systematic-debuggingRef
02f077c174c5335e2f5d02ca15e77b70d9543e58
Maintenance freshness
7/18/2026
Usage
57 downloads · 235 views
File structure