debug-issues

Diagnoses bugs by tracing symptoms to root causes using CoD^Σ reasoning framework.

1|Updated Oct 26, 2025
One-click install
npx skills add https://github.com/yangsi7/fine-tuning-exercise-generation --skill debug-issues
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug-issues
Source: https://github.com/yangsi7/fine-tuning-exercise-generation/tree/main/.claude/skills/debug-issues
Command: npx skills add https://github.com/yangsi7/fine-tuning-exercise-generation --skill debug-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a systematic, intelligence-first approach to debugging. It traces from a reported symptom to the root cause, parses error messages, leverages code intelligence, and proposes validated fixes, significantly reducing debugging time and effort.

Core Features & Use Cases

  • Systematic Root Cause Analysis: Captures symptoms, parses error messages (type, file:line, stack trace), and uses project-intel.mjs to trace dependencies and identify the exact source of the bug.
  • CoD^Σ Trace & MCP Verification: Documents a complete Chain-of-Thought (CoD^Σ) reasoning chain and verifies findings against authoritative sources (MCP) for transparent, evidence-backed diagnoses.
  • Comprehensive Bug Report: Generates a detailed bug-report.md including symptom, root cause, fix specification (with code changes), and a verification plan, ready for implementation.
  • Use Case: If a user reports a "TypeError: Cannot read property 'discount' of undefined" during checkout, this Skill will pinpoint the missing null check at src/pricing/calculator.ts:67, explain why it fails, and provide the exact code fix with a test plan.

Quick Start

Use the debug-issues skill to diagnose the 'TypeError' in the attached error log.

Frequently Asked Questions about debug-issues

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

FAQPage Schema
How do I trace a bug from error message to root cause in my code?

Root cause analysis traces symptoms through error parsing and code intelligence to pinpoint the exact source. This Skill captures the error message, parses type and stack trace, uses project dependencies to identify the failing line, and documents the complete reasoning chain so you understand why the bug occurs and how to fix it.

What's the best way to diagnose a TypeError or unexpected behavior in production?

Systematic debugging diagnoses production errors by parsing symptoms, extracting file:line references from stack traces, and tracing dependencies to the root cause. This Skill generates a structured bug report with the exact failure point, evidence chain, and validated fix proposal, reducing diagnosis time significantly.

Can I use debugging to generate a bug report with fix proposals ready for implementation?

Yes. This Skill produces a comprehensive bug report including the symptom, root cause identification, fix specification with code changes, and a verification plan. The output is immediately actionable for your team to implement and test.

How do I verify my bug diagnosis is correct before implementing a fix?

The Skill documents a complete Chain-of-Thought reasoning trace and verifies findings against authoritative sources, creating transparent, evidence-backed diagnoses. This verification chain lets you confirm the diagnosis logic before committing to code changes.

Does debugging work across different types of applications like web apps, APIs, and backend services?

Yes. This Skill systematically diagnoses bugs across web applications, APIs, and backend services. The root cause analysis and error parsing methods apply to any codebase where you have a symptom, error log, or unexpected behavior to investigate.

What information do I need to provide to diagnose a bug?

Provide the reported symptom, error message, stack trace, or description of unexpected behavior. The Skill parses these inputs, traces dependencies and code flow, and identifies the exact root cause with supporting evidence to guide your fix.