diagnosis

Diagnose software defects by analyzing symptoms and investigating the codebase.

Updated Dec 29, 2025
One-click install
npx skills add https://github.com/yumayo/MasterDataEditor --skill diagnosis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diagnosis
Source: https://github.com/yumayo/MasterDataEditor/tree/main/.claude/skills/diagnosis
Command: npx skills add https://github.com/yumayo/MasterDataEditor --skill diagnosis

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps identify the root cause of software bugs by analyzing symptoms and investigating the codebase.

Core Features & Use Cases

  • Root Cause Analysis: Pinpoints the underlying reasons for reported issues.
  • Codebase Investigation: Scans code to validate hypotheses and gather evidence.
  • Actionable Recommendations: Provides concrete steps for fixing the bug.
  • Use Case: When a user reports that a feature is crashing, this Skill can analyze the error message and relevant code sections to determine why the crash is occurring and suggest a fix.

Quick Start

Use the diagnosis skill to find the root cause of the bug described in the following report.

Frequently Asked Questions about diagnosis

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

FAQPage Schema
How do I find the root cause of a software bug in my codebase?

Bug diagnosis works by analyzing user-reported symptoms and scanning the codebase to gather evidence, generating hypotheses to pinpoint the underlying reasons for the software defect.

What is the best way to investigate a crashing feature and suggest a fix?

Codebase investigation scans your code to validate hypotheses and gather evidence, applying a structured approach to pinpoint the origin of bugs and provide actionable recommendations for fixing them.

How do I troubleshoot software defects using AI for code investigation?

AI-driven bug diagnosis analyzes user-reported symptoms and investigates the codebase to identify root causes, applying structured hypothesis generation and evidence gathering to pinpoint defect origins.

Can I use automated root cause analysis for any software development debugging workflow?

Yes, automated root cause analysis applies to debugging and issue resolution workflows within software development, diagnosing defects by analyzing symptoms and investigating the codebase to propose solutions.

What steps are needed to diagnose code defects from user-reported symptoms?

Diagnosing code defects requires a structured approach: analyzing user-reported symptoms, generating hypotheses, investigating the codebase to gather evidence, and proposing actionable solutions to fix the bug.