skills.rest
bigeasyfreeman
bigeasyfreemanCOMMUNITY
Explore all skills by this author →
GitHub

debug

Guide engineers through a phased debugging workflow and output a structured investigation report.

18|1|Updated Dec 19, 2025
Search Tags:#debugging#documentation#investigation#diagnostics#phases#root-cause
One-click install
npx skills add https://github.com/bigeasyfreeman/agent-framework --skill debug-bigeasyfreeman
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/bigeasyfreeman/agent-framework/tree/main/templates/claude/.claude/skills/_DEBUG
Command: npx skills add https://github.com/bigeasyfreeman/agent-framework --skill debug-bigeasyfreeman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides engineers through a structured debugging session to rapidly diagnose software issues with a repeatable protocol.

Core Features & Use Cases

  • Evidence gathering: Collect exact error messages, environment details, and steps to reproduce.
  • Hypothesis-driven debugging: Form and test hypotheses in a structured sequence.
  • Phase-based workflow: Follow Gather Evidence, Form Hypotheses, Test Hypotheses, and Fix and Verify to reach a root-cause report.
  • Documentation: Produce a clear investigation log and final root-cause summary for future reference.

Quick Start

To start a debugging session, describe the symptoms and environment to the skill and request a structured diagnostic plan.

Frequently Asked Questions about debug

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

FAQPage Schema
What is a structured debugging workflow for software investigation?▼

A structured debugging workflow guides engineers through evidence gathering, hypothesis formation, testing, and verification to reach a root-cause diagnosis for software faults.

How do I start a structured debugging session for a software fault?▼

To start a debugging session, describe the exact error messages, environment details, and reproduction steps to receive a structured diagnostic plan for systematic investigation.

How do I form and test hypotheses during root-cause investigation?▼

During root-cause investigation, you form hypotheses based on gathered evidence and test them systematically in a structured sequence before applying fixes within a phased workflow.

Can I get a documented investigation report after diagnosing software issues?▼

Yes, the debugging process produces a structured investigation log and a final root-cause summary report, providing clear documentation of the software issue for future reference.

What are the phases of a systematic debugging protocol?▼

The systematic debugging protocol consists of four phases: Gather Evidence, Form Hypotheses, Test Hypotheses, and Fix and Verify, ensuring a repeatable diagnostic process.

Related Skills

Explore More Software Engineering Skills→
Clay-HHKClay-HHK
2

bug-detective

Diagnose code errors from error messages, logs, and stack traces.

Community
Intermediate
singhianand23045singhianand23045

gstack-openclaw-investigate

Diagnose software bugs through a structured four-phase root-cause investigation.

Community
Advanced
SyloReiSyloRei
3

debug

Automate a four-phase debugging workflow to reproduce, hypothesize, isolate, and verify fixes.

Community
Advanced
Proxy2021Proxy2021
5

error_monitor

Aggregate Enso error and action logs into a real-time monitoring dashboard.

Community
Advanced