easysdd-issue-analyze

Analyze bug reports and code to localize root causes to file:line.

1.1k|82|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/liuzhengdongfortest/easysdd --skill easysdd-issue-analyze
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: easysdd-issue-analyze
Source: https://github.com/liuzhengdongfortest/easysdd/tree/main/easysdd-issue-analyze
Command: npx skills add https://github.com/liuzhengdongfortest/easysdd --skill easysdd-issue-analyze

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns a confirmed issue report and repository code into a concrete root cause analysis so the user can choose an appropriate repair path rather than guessing or directly editing code. It prevents wasted effort by forcing code reading, precise localization to file:line, and a clear impact assessment before any fix is applied.

Core Features & Use Cases

  • Precise localization: Grep and read code referenced by report.md to point to exact file:line locations that are likely the cause.
  • Failure path reconstruction: Restore normal and failing execution paths to identify the code branch where the defect manifests.
  • Impact and repair options: Classify the root cause, evaluate affected modules and data risk, and present 2-3 repair options with pros/cons so the user can decide.
  • Use Case: When a user says "analyze this bug" and the issue folder contains a confirmed report.md, run the five-step analysis to produce an issue-analysis draft for user approval.

Quick Start

Analyze the confirmed issue by reading report.md and the repository code, identify the root cause down to file:line, evaluate impact, and present 2-3 repair options for the user to choose from.

Frequently Asked Questions about easysdd-issue-analyze

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

FAQPage Schema
How do I locate the root cause of a bug from a confirmed issue report?

To locate the root cause of a bug, analyze the confirmed issue report and repository code to reconstruct failing execution paths and pinpoint exact file:line locations. This prevents wasted effort by forcing code reading and precise localization before applying a fix.

What is the best way to assess bug impact and evaluate repair options?

The best way to assess bug impact is to classify the root cause type and evaluate affected modules alongside data risk. This analysis enumerates 2-3 repair proposals with tradeoffs, enabling users to evaluate repair options and choose an appropriate path.

How do I analyze code to identify failing paths in a repository?

To analyze code and identify failing paths, grep and read the code referenced by the issue report. This restores normal and failing execution branches to locate the exact code where the defect manifests, ensuring accurate bug analysis.

Do I need a specific file format to start a bug analysis?

Yes, you need a confirmed report.md file located in the issue directory to start the bug analysis. This report provides the necessary context to inspect repository code, reproduce the failure, and assess repair options.

Why classify root cause type when analyzing a confirmed bug report?

Classifying the root cause type when analyzing a confirmed bug report evaluates the severity and impact on affected modules and data risk. This classification directly informs the 2-3 proposed repair options and their respective tradeoffs for user selection.