debugging-systematic

Diagnose software issues through root-cause analysis with hypotheses and logging.

Updated Jul 29, 2025
One-click install
npx skills add https://github.com/T1nker-1220/.claude --skill debugging-systematic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debugging-systematic
Source: https://github.com/T1nker-1220/.claude/tree/main/skills/debugging-systematic
Command: npx skills add https://github.com/T1nker-1220/.claude --skill debugging-systematic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the common pitfall of jumping to solutions without proper diagnosis, which often leads to fixing symptoms instead of root causes, wasting time and reintroducing bugs.

Core Features & Use Cases

  • Root Cause Analysis: Guides you through a systematic workflow to identify the true source of a bug, including generating multiple hypotheses and distilling them to the most likely causes.
  • Strategic Validation: Utilizes strategic logging and direct database validation via MCP servers (Firebase, PostgreSQL, Supabase) to confirm diagnoses with real-time data.
  • Use Case: When a user reports an error like "Cannot read property 'imageUrl' of undefined," this skill will systematically gather information, propose 5-7 hypotheses, narrow them down, and use MCP servers to validate database schema or data issues before suggesting a fix.

Quick Start

Ask Claude to systematically debug an issue:

I'm getting an error: "Cannot read property 'imageUrl' of undefined" when trying to access dating features. Can you help me debug this systematically?

Example MCP query for Firebase:

firebase_query({ collection: "users", documentId: "user123" })

Frequently Asked Questions about debugging-systematic

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

FAQPage Schema
How do I systematically debug an error instead of just applying quick fixes?

Systematic debugging involves generating multiple hypotheses about the root cause, narrowing them to the most likely 1-2 candidates, then validating with strategic logging and real data before fixing. This approach prevents wasting time on symptom fixes that reintroduce bugs later.

Can I use database validation to confirm what's causing my bug?

Yes. Root-cause analysis includes querying your database directly via MCP servers—Firebase, PostgreSQL, or Supabase—to validate schema and data state. This confirms whether the issue originates in data layer, backend logic, or frontend code.

What's the best way to diagnose bugs across backend, frontend, API, and database layers?

A structured workflow generates 5-7 hypotheses, distills them to the likeliest causes, adds strategic logging to test assumptions, validates findings against live data, and confirms the diagnosis before applying fixes. This method works across all application layers.

How do I know if I'm fixing the real problem or just treating symptoms?

Systematic root-cause analysis distinguishes symptom fixes from real solutions by requiring hypothesis generation, data validation, and diagnosis confirmation. Jumping to fixes without this workflow typically means you're treating symptoms, not causes.

Do I need to write logging code to diagnose bugs effectively?

Strategic logging is a core part of validation—it lets you test assumptions and trace execution flow. Combined with direct database queries via MCP servers, logging provides evidence to confirm the actual root cause before deploying a fix.