skills.rest
WillNigri
WillNigriCOMMUNITY
Explore all skills by this author →
𝕏@willnigriGitHub

debug

Guides systematic debugging from symptom to verified root cause via a four-phase model.

33|6|Updated Mar 17, 2026
Search Tags:#debugging#investigation#analysis#hypothesis#root-cause#regression-testing#production-issues
One-click install
npx skills add https://github.com/WillNigri/Agentic-Tool-Optimization --skill debug-willnigri
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/WillNigri/Agentic-Tool-Optimization/tree/main/.claude/skills/debug
Command: npx skills add https://github.com/WillNigri/Agentic-Tool-Optimization --skill debug-willnigri

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides engineers through systematic debugging to identify root causes before applying fixes, preventing patchwork solutions.

Core Features & Use Cases

  • Phase-driven workflow: investigate, analyze, hypothesize, and implement to structure debugging.
  • Root-cause focus: enforces the Iron Law that no fix should be attempted without a verified root cause.
  • Pattern-based analysis: supports documenting symptoms, hypotheses, tests, and outcomes to improve post-mortem.
  • Use Case: when a bug regresses after deployment, this skill guides triage and robust root-cause verification.

Quick Start

Initiate the root-cause investigation by outlining the observed failure, then follow the four phases: investigate, analyze, hypothesize, implement.

Frequently Asked Questions about debug

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

FAQPage Schema
How do I find a root cause before applying a bug fix?▼

To find a root cause before fixing a bug, follow a phase-driven workflow covering investigation, analysis, hypothesis, and implementation. This systematic debugging approach enforces verifying root causes before attempting any fixes.

What is the best way to structure debugging efforts for unclear symptoms?▼

The best way to structure debugging for unclear symptoms is a formal workflow with phases for investigation, analysis, hypothesis, and implementation. This method documents symptoms, hypotheses, tests, and outcomes to resolve multiple suspects systematically.

How do I triage production issues and prevent patchwork solutions?▼

Triage production issues and prevent patchwork solutions by initiating a root-cause investigation that outlines observed failures. Structured debugging ensures sustainable, verifiable fixes rather than temporary patches during incident response.

How can I verify a bug regression after deployment?▼

Verify a bug regression after deployment by applying a pattern-based analysis workflow that documents symptoms and outcomes. This guides triage and robust root-cause verification to ensure the fix is sustainable and regression tests are implemented.

When should I use a hypothesis-driven investigation for debugging?▼

Use hypothesis-driven investigation for debugging when symptoms are unclear or multiple suspects exist. It supports documenting tests and outcomes to improve post-mortem analysis and ensure verifiable, root-cause fixes.

Related Skills

Explore More Software Engineering Skills→
rahmanayonrahmanayon

investigate

Plan root-cause investigations across investigate, analyze, hypothesize, and implement phases.

Community
Advanced
tomguntomgun

fixing-bugs

Reproduce bugs with regression tests and apply minimal root-cause fixes.

Community
Intermediate
TheBushidoCollectiveTheBushidoCollective
187

sentry-alerts-issues

Manage Sentry alert rules, issue triage, and notification routing across projects.

Official
Advanced
jossteijosstei
453

debug-workflow

Coordinate specialist debugger agents through a structured five-step evidence-gathering workflow.

Community
Intermediate