skills.rest
walker-hzx
walker-hzxCOMMUNITY
Explore all skills by this author →
GitHub

debugging

Diagnose software bugs through evidence collection and root-cause analysis.

Updated Feb 19, 2026
Search Tags:#debugging#troubleshooting#diagnostics#reproducibility#software-engineering#root-cause-analysis
One-click install
npx skills add https://github.com/walker-hzx/AI-Assistant --skill debugging-walker-hzx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debugging
Source: https://github.com/walker-hzx/AI-Assistant/tree/main/skills/debugging
Command: npx skills add https://github.com/walker-hzx/AI-Assistant --skill debugging-walker-hzx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

A structured, evidence-based approach to locating and fixing bugs, replacing guesswork with repeatable, verifiable processes.

Core Features & Use Cases

  • Evidence-driven diagnosis: collects data, forms testable hypotheses, and validates fixes.
  • End-to-end debugging support: applicable to frontend, backend, and integration bugs with clear replication steps.
  • Comprehensive documentation: records findings and outcomes to prevent regressions.

Quick Start

Start a debugging session by outlining the observed issue and instructing the agent to collect evidence, reproduce the bug, and confirm a root cause.

Frequently Asked Questions about debugging

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

FAQPage Schema
What is the best way to perform root-cause analysis for a software bug?▼

Root-cause analysis is best performed using an evidence-based approach that collects data, forms testable hypotheses, and validates fixes to replace guesswork with repeatable processes.

How do I reproduce a bug systematically across frontend and backend systems?▼

To reproduce a bug systematically, outline the observed issue and collect evidence to establish clear replication steps across frontend, backend, and full-stack integration components.

How do I structure a step-by-step diagnostic workflow for troubleshooting?▼

A structured diagnostic workflow for troubleshooting guides you stepwise through bug reproduction, evidence collection, hypothesis validation, and verification to improve debugging efficiency.

Can I use structured debugging for full-stack integration issues?▼

Yes, structured debugging is applicable to software engineering tasks across frontend, backend, and full-stack integration systems, providing clear replication steps and rigorous validation.

Why do I need to document findings during root-cause analysis?▼

Documenting findings during root-cause analysis records outcomes and prevents regressions by ensuring the diagnostic workflow, evidence, and verified fixes are thoroughly preserved.

Related Skills

Explore More Software Engineering Skills→
mattdurhammattdurham
9

debugger

Collect logs and traces to diagnose software issues and write reports to bots/debug.md.

Community
Advanced
cosmixcosmix
53

debugging

Diagnose and resolve software bugs across programming languages and environments.

Community
Intermediate
d-o-hubd-o-hub
11

rust-code-quality

Review Rust code quality across eight dimensions including async patterns and error handling.

Community
Advanced
adryanmoldokkr32-pixeladryanmoldokkr32-pixel

canary

Monitor live applications for post-deploy errors, latency spikes, and page failures.

Community
Advanced