skills.rest
fppfurtado
fppfurtadoCOMMUNITY
Explore all skills by this author →
GitHub

debug

Diagnoses root causes of symptoms from structured input with evidence-backed conclusions.

Updated Apr 30, 2026
Search Tags:#evidence#diagnose#triage#root-cause#hypotheses#symptom
One-click install
npx skills add https://github.com/fppfurtado/pragmatic-dev-toolkit --skill debug-fppfurtado
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/fppfurtado/pragmatic-dev-toolkit/tree/main/skills/debug
Command: npx skills add https://github.com/fppfurtado/pragmatic-dev-toolkit --skill debug-fppfurtado

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnostically identifies root causes of observed symptoms using a scientific, diagnostic workflow, producing a diagnosis and evidence without proposing or applying fixes.

Core Features & Use Cases

  • Systematic symptom intake: collect, reproduce, hypothesize, and gather evidence to guide triage decisions.
  • Evidence-based diagnosis: outputs a concise root-cause with supporting rationale and scope of impact.
  • Non-prescriptive: explicitly avoids prescribing fixes, deferring remediation decisions to operators or higher-level processes.

Quick Start

Describe the observed symptom in detail and the skill will produce a root-cause diagnosis with supporting evidence.

Frequently Asked Questions about debug

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

FAQPage Schema
How do I diagnose the root cause of a test failure or runtime error?▼

Diagnosing root causes involves systematic symptom intake where you collect, reproduce, hypothesize, and gather evidence. This skill processes structured symptom input to produce evidence-backed conclusions and guide triage decisions without prescribing fixes.

Can I use this to find fixes for divergent behavior across local, CI, and production environments?▼

This skill diagnoses root causes of divergent behavior across local, CI, and production environments but explicitly avoids proposing fixes. It defers remediation decisions to operators, outputting a concise diagnosis with supporting rationale and scope of impact instead.

What is the best way to triage observed symptoms before planning remediation?▼

The best way to triage observed symptoms is applying a scientific diagnostic workflow that requires structured symptom input and logical reasoning steps. This generates an evidence-based diagnosis with supporting rationale to guide triage and ADR planning.

Do I need to provide structured input to perform an evidence-based diagnosis?▼

Yes, you need to provide structured symptom input describing the observed symptom in detail. The skill requires this input alongside logical reasoning steps to produce an evidence-backed root-cause diagnosis.

Why does this diagnostic process avoid prescribing fixes for runtime errors?▼

The diagnostic process avoids prescribing fixes to remain non-prescriptive, deferring remediation decisions to operators or higher-level processes. It focuses entirely on identifying the root cause and providing supporting evidence rather than applying solutions.

Related Skills

Explore More Software Engineering Skills→
jbaranskijbaranski

jeff-skill-error-debugging-rca

Diagnose software bugs by enforcing root-cause analysis before fixes.

Community
Advanced
jfmyers9jfmyers9
8

diagnose

Diagnose bugs, incidents, and CI failures with read-only root-cause reports.

Community
Intermediate
gensart-projsgensart-projs

performance-profiling

Measure Lighthouse scores and core web vitals to identify performance bottlenecks.

Community
Intermediate
Kit4SomeKit4Some
4

qa

Run automated tests, triage failures, and verify atomic fixes.

Community
Advanced