aiskillstore/systematic-debugging
skills/dmjgilbert/systematic-debugging/SKILL.md
Four-phase root cause investigation before attempting fixes. Use when debugging bugs, test failures, or unexpected behavior.
$ install --global
skillsauthnpx skillsauth add aiskillstore/marketplace systematic-debuggingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 1, 2026, 12:18 PM56.7s2 files scanned
SKILL.md
- name:
- systematic-debugging
- description:
- Four-phase root cause investigation before attempting fixes. Use when debugging bugs, test failures, or unexpected behavior.
Systematic Debugging
ALWAYS find root cause before attempting fixes. Symptom fixes are failure.
When to Use
- Encountering bugs or test failures
- Unexpected behavior in code
- Before proposing any fix
The Four Phases
Phase 1: Root Cause Investigation
Before proposing any solution:
- Read error messages thoroughly - Don't skip warnings or stack traces; they often contain exact solutions
- Reproduce consistently - Verify you can trigger the issue reliably with documented steps
- Check recent changes - Examine
git diff, dependencies, and configuration modifications - Gather diagnostic evidence - In multi-component systems, add instrumentation at component boundaries
- Trace data flow - Backward trace from the error to find where bad values originate
Phase 2: Pattern Analysis
Establish the pattern before fixing:
- Locate similar working code in the codebase
- Read reference implementations completely (not skimmed)
- List every difference between working and broken code
- Understand all dependencies and assumptions
Phase 3: Hypothesis Testing
Apply scientific method:
- State your hypothesis clearly: "I believe X is failing because Y, evidenced by Z"
- Test with the smallest possible change
- Change only ONE variable at a time
- Verify results before proceeding
Phase 4: Implementation
Fix the root cause systematically:
- Create a failing test case first (TDD)
- Implement a single fix addressing only the root cause
- Verify the fix resolves the issue without breaking other tests
- If fix doesn't work, return to Phase 1
Red Flags - STOP Immediately
- Proposing fixes without understanding the issue
- Attempting multiple simultaneous changes
- Assuming problems without verification
- Skipping evidence gathering
- Making "quick fixes" before investigation
When 3+ Fixes Fail
STOP. This signals an architectural problem, not a fixable bug:
- Do not attempt another fix
- Return to Phase 1
- Question whether the underlying pattern/design is sound
- Ask: "Should we refactor architecture vs. continue fixing symptoms?"
Random fixes waste time and create new bugs. Quick patches mask underlying issues.
Results
Systematic approach: 15-30 minutes to resolution with 95% first-time success vs. Trial-and-error: 2-3 hours of thrashing with 40% success and new bugs introduced
Related Skills
aiskillstore/hig-components-content
development
VerifiedTrustedCommunity
Apple Human Interface Guidelines for content display components. Use this skill when the user asks about charts component, collection view, image view, web view, color well, image well, activity view, lockup, data visualization, content display, displaying images, rendering web content, color pickers, or presenting collections of items in Apple apps. Also use when the user says how should I display charts, what's the best way to show images, should I use a web view, how do I build a grid of items, what component shows media, or how do I present a share sheet. Cross-references: hig-foundations for color/typography/accessibility, hig-patterns for data visualization patterns, hig-components-layout for structural containers, hig-platforms for platform-specific component behavior.
244SKILL.mdUpdated Apr 10, 2026
aiskillstore/helpdesk-automation
tools
VerifiedTrustedCommunity
Automate HelpDesk tasks via Rube MCP (Composio): list tickets, manage views, use canned responses, and configure custom fields. Always search tools first for current schemas.
244SKILL.mdUpdated Apr 10, 2026
aiskillstore/haskell-pro
testing
VerifiedTrustedCommunity
Expert Haskell engineer specializing in advanced type systems, pure functional design, and high-reliability software. Use PROACTIVELY for type-level programming, concurrency, and architecture guidance.
244SKILL.mdUpdated Apr 10, 2026
aiskillstore/graphql
tools
VerifiedTrustedCommunity
GraphQL gives clients exactly the data they need - no more, no less. One endpoint, typed schema, introspection. But the flexibility that makes it powerful also makes it dangerous. Without proper controls, clients can craft queries that bring down your server. This skill covers schema design, resolvers, DataLoader for N+1 prevention, federation for microservices, and client integration with Apollo/urql. Key insight: GraphQL is a contract. The schema is the API documentation. Design it carefully.
244SKILL.mdUpdated Apr 10, 2026