diagnose

Trace bug symptoms to the responsible file and approximate line.

11.6k|1.1k|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/emdash-cms/emdash --skill diagnose-emdash-cms
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diagnose
Source: https://github.com/emdash-cms/emdash/tree/main/.flue/skills/diagnose
Command: npx skills add https://github.com/emdash-cms/emdash --skill diagnose-emdash-cms

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly identify the exact code location responsible for a symptom by tracing from reproduce notes to a file and approximate line, enabling fast debugging without modifying source.

Core Features & Use Cases

  • Anchor on the reproduce notes to start tracing.
  • Walk from the symptom through stack traces and code paths to pinpoint the responsible file and line.
  • Output a concise root-cause explanation and a confidence rating to guide fixes.

Quick Start

Anchor on the reproduce notes and trace the symptom to the exact source file and line.

Frequently Asked Questions about diagnose

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

FAQPage Schema
How do I trace a bug from a stack trace to the exact source file and line?

To trace a bug, anchor on reproduce notes and walk from the symptom through stack traces and code paths to pinpoint the responsible file and approximate line, providing a root-cause explanation with a confidence rating.

What is the best way to identify the root cause of an exception without modifying source code?

The best way to identify a root cause is by reading code without modifying source files or making external calls, tracing from reproduce notes through code paths to deliver a clear root-cause location with a confidence rating.

Can I diagnose wrong outputs and failing tests using reproduce notes and code paths?

Yes, you can diagnose wrong outputs and failing tests by anchoring on reproduce notes to start tracing symptoms through stack traces and code paths to locate the exact root cause in the codebase.

Does root-cause bug investigation work for typical symptoms like exceptions and failing tests?

Root-cause bug investigation works for typical symptoms such as exceptions, wrong outputs, or failing tests by using stack traces and code paths to locate the responsible file and line in a codebase.

What are the limitations of tracing symptoms to the root cause in code?

Limitations include reading code without modifying source files and avoiding external calls, meaning it strictly delivers a root-cause location and confidence rating rather than applying fixes or running dynamic tests.