skills.rest
fernando-fernandez3
fernando-fernandez3COMMUNITY
Explore all skills by this author →
GitHub

debug

Guide a reproduce-isolate-trace-hypothesize-fix-prevent debugging workflow.

Updated Aug 27, 2026
Search Tags:#debugging#trace#reproduce#hypothesis#tests#isolate
One-click install
npx skills add https://github.com/fernando-fernandez3/claude-code-resources --skill debug-fernando-fernandez3
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/fernando-fernandez3/claude-code-resources/tree/main/my-config/skills/debug
Command: npx skills add https://github.com/fernando-fernandez3/claude-code-resources --skill debug-fernando-fernandez3

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured, repeatable debugging protocol that guides users through reproduction, isolation, tracing, hypothesis testing, fixes, and preventive measures, reducing guesswork and speeding up incident resolution.

Core Features & Use Cases

  • Systematic steps: Reproduce, Isolate, Trace, Hypothesize, Fix, Prevent.
  • Repro tooling guidance: templates and examples to reproduce bugs and verify fixes.
  • Use cases: debugging software defects, data pipeline issues, and integration failures where deterministic reasoning accelerates resolution.

Quick Start

To begin, issue a command like /debug "TypeError: NoneType object is not subscriptable in process_user" and follow the six-step workflow to reproduce, isolate, trace, hypothesize, fix, and prevent.

Frequently Asked Questions about debug

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

FAQPage Schema
What is structured debugging and when should I use it?▼

Structured debugging enforces a deterministic workflow—reproduce, isolate, trace, hypothesize, fix, prevent—to resolve software defects, data-pipeline issues, and integration failures while reducing guesswork.

How do I debug a TypeError using a reproduce-isolate-trace workflow?▼

To debug a TypeError, issue a command with the error details and follow the six-step workflow: reproduce the bug, isolate the component, trace execution, hypothesize the cause, fix it, and add validation tests to prevent recurrence.

Can I use this structured debugging approach for data pipeline issues and integration faults?▼

Yes, this structured debugging approach applies directly to data-pipeline issues and integration faults. It uses deterministic workflows and minimal hypotheses to accelerate incident resolution across these contexts.

What's the best way to reproduce bugs and verify fixes during software debugging?▼

The best way to reproduce bugs and verify fixes is using repro tooling guidance, which provides templates and examples to reliably trigger defects and confirm that your applied fixes resolve the issue.

Why does guessing root causes slow down incident resolution compared to hypothesis testing?▼

Guessing root causes slows incident resolution because it lacks deterministic validation. Structured debugging enforces minimal hypotheses and validation tests, ensuring you confirm the exact failure point before applying a fix.

Related Skills

Explore More Software Engineering Skills→
gajjalaashok75-UIgajjalaashok75-UI
2

error-diagnostics-smart-debug

Diagnose software errors by analyzing logs, stack traces, and failure patterns.

Community
Advanced
DYAI2025DYAI2025

regression-test-generator

Generate Arrange-Act-Assert regression tests for Jest, Vitest, pytest, or Playwright.

Community
Intermediate
muratcankoylanmuratcankoylan
8

BACKPRESSURE

Create deterministic self-verification checks for AI coding agents.

Community
Intermediate
iciakkyiciakky

debug

Diagnoses root causes of code modifications using a seven-step debugging workflow and generates verified fix plans.

Community
Intermediate