sfermanelli-debug

Trace root causes of software defects through structured investigation workflows.

1|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/sebafermanelli/sfermanelli-skills --skill sfermanelli-debug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sfermanelli-debug
Source: https://github.com/sebafermanelli/sfermanelli-skills/tree/main/sfermanelli-debug
Command: npx skills add https://github.com/sebafermanelli/sfermanelli-skills --skill sfermanelli-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Investigate and fix bugs by tracing root causes, not just symptoms. Use this skill when the user reports a bug, error, unexpected behavior, or something that "doesn't work". Triggers for "this is broken", "why isn't this working", "I'm getting an error", "it crashes when", "unexpected behavior", "this used to work", "can you debug this", stack traces, error screenshots, or any problem-solving scenario. Different from fix-lint (which is automated) — this is investigation and diagnosis.

Core Features & Use Cases

  • Structured root-cause debugging: guide reproduction, isolation, and evidence-based diagnosis.
  • Step-by-step investigation workflow: reproduce, isolate, diagnose, verify, and document a fix plan.
  • Real-world use: you encounter a failing feature in a web app; you get a guided, evidence-driven path to root cause and a clear remediation plan.

Quick Start

Provide a bug report with steps to reproduce and I will guide you through a structured root-cause debugging process.

Frequently Asked Questions about sfermanelli-debug

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

FAQPage Schema
How do I debug software by tracing the root cause instead of just fixing symptoms?

To debug by tracing root causes, you need a structured investigation workflow that reproduces the issue, isolates variables, diagnoses evidence, and verifies a documented fix plan.

What is the best way to investigate unexpected behavior or crashes in API integrations?

The best way to investigate unexpected behavior in API integrations is following an evidence-driven path that reproduces the defect and isolates the root cause across services.

How do I systematically reproduce and isolate a reported error in my web app?

You systematically reproduce and isolate a reported error by guiding the investigation step-by-step from reproduction to isolation, yielding an evidence-backed diagnosis and remediation plan.

Does this structured debugging approach work for both frontend and backend services?

Yes, this structured debugging approach works for frontend, backend, services, and API integrations, diagnosing crashes and unexpected behavior across all development stages.

When should I use a root-cause diagnosis workflow instead of automated lint fixing?

You should use a root-cause diagnosis workflow instead of automated lint fixing when you need to investigate why something is broken, trace unexpected behavior, and document a fix plan.

What do I need to provide to start a structured root-cause debugging process?

To start a structured root-cause debugging process, you need to provide a bug report with steps to reproduce the error, crash, or unexpected behavior you are experiencing.