skills.rest
joshsymonds
joshsymondsCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

debugging

Guide evidence-based debugging with root cause analysis and regression tests.

Updated Jan 23, 2026
Search Tags:#testing#debugging#troubleshooting#root cause analysis#bug fixing#regression
One-click install
npx skills add https://github.com/joshsymonds/gambit --skill debugging-joshsymonds
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debugging
Source: https://github.com/joshsymonds/gambit/tree/main/skills/debugging
Command: npx skills add https://github.com/joshsymonds/gambit --skill debugging-joshsymonds

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and scripts (resource) components.

What problem does it solve?

This Skill provides a structured, evidence-based approach to identifying and fixing bugs, preventing quick fixes that mask underlying issues and ensuring robust solutions.

Core Features & Use Cases

  • Systematic Investigation: Follows a 6-phase process from task creation to closure, emphasizing root cause analysis over symptom fixing.
  • Evidence-Based Fixes: Requires concrete evidence (logs, tests, code) before and after fixes.
  • Regression Prevention: Mandates writing failing tests before fixing and running the full test suite afterward.
  • Use Case: When a critical bug is reported, this Skill ensures the team doesn't just patch the immediate error but thoroughly investigates its origin, writes a test to guarantee it won't reappear, and verifies the fix against the entire codebase.

Quick Start

Use the debugging skill to systematically investigate and fix the reported bug.

Frequently Asked Questions about debugging

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is systematic root cause analysis for bug fixing?▼

Systematic root cause analysis for bug fixing is a structured, evidence-based approach to identifying the origin of software failures rather than patching symptoms. It uses logs, tests, and code exploration to ensure robust resolutions.

How do I fix a bug without causing a regression?▼

To fix a bug without causing a regression, write a failing unit test that reproduces the issue, apply the fix, and then run the full test suite to verify the correction against the entire codebase.

How do I troubleshoot unexpected software behavior systematically?▼

To troubleshoot unexpected software behavior systematically, follow a multi-phase process from task creation to closure, gathering concrete evidence like logs and tests before and after applying fixes to verify the resolution.

Can I use this debugging approach with my existing testing frameworks?▼

Yes, this debugging approach integrates with existing testing frameworks and code exploration agents. It mandates writing failing tests before fixing errors to guarantee thoroughness and prevent future regressions.

What's the best way to investigate software bugs?▼

The best way to investigate software bugs is an evidence-based approach requiring concrete logs, tests, and code verification before and after fixes, preventing quick patches that mask underlying root causes.

Related Skills

Explore More Software Engineering Skills→
sQVesQVe

debug-issue

Diagnose bugs by tracing evidence and generating a BR issue template.

Community
Advanced
multiversxmultiversx
12

fix_verification

Verify smart contract bug fixes by running Mandos scenarios and regression tests.

Official
Intermediate
mwaymway
4

systematic-debugging

Identify root causes of bugs and test failures through a four-phase debugging workflow.

Community
Advanced
abranjithabranjith

fix

Diagnose software bugs, apply minimal fixes, and add regression tests.

Community
Advanced