skills.rest
joshsmithxrm
joshsmithxrmCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

debug

Enforce a four-phase root-cause investigation workflow before proposing fixes.

5|1|Updated Dec 14, 2025
Search Tags:#debugging#quality-assurance#software-development#phases#root-causes
One-click install
npx skills add https://github.com/joshsmithxrm/power-platform-developer-suite --skill debug-joshsmithxrm
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/joshsmithxrm/power-platform-developer-suite/tree/main/.claude/skills/debug
Command: npx skills add https://github.com/joshsmithxrm/power-platform-developer-suite --skill debug-joshsmithxrm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging guided by a disciplined root-cause investigation workflow to reduce time spent on triage and prevent premature fixes.

Core Features & Use Cases

  • Enforces a four-phase Root Cause Investigation workflow to ensure reproducibility, evidence gathering, and analysis before proposing fixes.
  • Provides guardrails and escalation rules to stop thrashing and improve repair quality across CLI, TUI, Extension, and MCP development modes.
  • Supports defense-in-depth and structured troubleshooting to improve long-term stability in software projects.

Quick Start

Start a guided debugging session by following the four-phase framework to identify root causes before proposing fixes.

Frequently Asked Questions about debug

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

FAQPage Schema
What is a systematic root-cause investigation workflow for debugging?▼

Systematic debugging enforces a four-phase root-cause investigation workflow that requires bug reproduction, evidence gathering, and analysis before proposing fixes. This structured approach prevents premature fixes and reduces triage time across software development contexts.

How do I debug defects across CLI, TUI, extension, and MCP environments?▼

Debugging across CLI, TUI, extension, and MCP environments follows a phased root-cause investigation workflow. It enforces evidence gathering and analysis before fixes, applying guardrails and escalation rules to stop thrashing and improve repair quality.

Why do my software fixes keep failing or causing new bugs?▼

Software fixes fail when root causes are not properly investigated before applying changes. A structured debugging workflow requires Phase 1 root-cause investigation before any fixes, with defined Phase 2-4 analysis and defense-in-depth checks to ensure long-term stability.

What's the best way to stop thrashing during software debugging?▼

The best way to stop thrashing during software debugging is to enforce guardrails and escalation rules within a structured root-cause investigation workflow. This ensures evidence gathering and analysis precede fixes, improving repair quality across development modes.

Does this debugging workflow support defense-in-depth checks for software stability?▼

Yes, the debugging workflow supports defense-in-depth and structured troubleshooting to improve long-term stability. It integrates phased analysis and escalation rules across CLI, TUI, extension, and MCP development contexts to ensure comprehensive defect resolution.

Can I use this systematic debugging approach for any software development project?▼

Yes, the systematic debugging approach applies across CLI, TUI, extension, and MCP development contexts. It enforces a root-cause investigation workflow with no dependencies, making it suitable for any software project requiring structured defect resolution.

Related Skills

Explore More Software Engineering Skills→
zillabunnyzillabunny

investigate

Reproduce a bug, trace its root cause, and document a verified fix plan.

Community
Advanced
mshaheerzmshaheerz
1

tool-systematic-debugging

Guide users through a four-phase debugging process to identify root causes.

Community
Advanced
redpanda-dataredpanda-data
34

tdd

Enforces a red-green-refactor cycle for writing and implementing tests with Vitest.

Official
Intermediate
Im5tuIm5tu
6

systematic-debugging

Identify root causes of software bugs through a four-phase debugging process.

Community
Advanced