cs-issue-analyze

Diagnose bug root causes by reading code and propose fix options.

Updated Jun 8, 2026
One-click install
npx skills add https://github.com/wildlily1021/XW_Software --skill cs-issue-analyze-wildlily1021
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cs-issue-analyze
Source: https://github.com/wildlily1021/XW_Software/tree/main/.agents/skills/cs-issue-analyze
Command: npx skills add https://github.com/wildlily1021/XW_Software --skill cs-issue-analyze-wildlily1021

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a bug report exists but the root cause is unknown, developers often guess or jump straight into fixing. This Skill enforces a disciplined analysis phase: actually reading the code, tracing the failure path, pinpointing the root cause at file:line level, and presenting 2-3 fix options for the user to choose before any code changes. ## Core Features & Use Cases - Code-Grounded Root Cause Analysis: Locates problem code via Grep/Glob, reconstructs the failure path, and classifies the root cause (logic error, state pollution, data format, concurrency, config, missing guard). - Impact Assessment: Evaluates blast radius, potentially affected modules, data integrity risks, and re-validates the severity rating from the original report. - Multiple Fix Proposals: Produces 2-3 fix options with pros, cons, and affected files, plus a recommended option, then waits for explicit user confirmation before any fix work begins. - Use Case: After a confirmed issue report ({slug}-report.md) exists, trigger this Skill to produce a structured {slug}-analysis.md with root cause and approved fix direction. ## Quick Start Ask the AI to analyze this bug and find the root cause based on the existing issue report, then present fix options for approval.

Frequently Asked Questions about cs-issue-analyze

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

FAQPage Schema
How do I find the root cause of a bug from an issue report?▼

Start from the report's reproduction steps, use Grep and Glob to locate the involved functions, then trace the call chain to find where the failure path diverges from the normal path. The divergence point is the root cause candidate, recorded as file:line.

What is a root cause analysis workflow for software bugs?▼

A structured workflow has five steps: locate the problem code, reconstruct the failure path, confirm and classify the root cause, assess the impact scope, and propose multiple fix options. Each step requires actually reading code rather than inferring from the bug description.

Does this analysis step modify any code?▼

No. This stage only reads code and produces an analysis document with fix options. Code changes happen in a separate fix stage, and only after the user explicitly confirms the root cause and chosen fix approach.

What types of root causes does bug analysis classify?▼

Root causes are classified into six categories: logic errors, state pollution, data format mismatches, concurrency or race conditions, configuration or environment issues, and missing defensive guards against null or empty inputs.

Why should bug analysis propose multiple fix options?▼

A single root cause often has several valid fixes with different trade-offs in scope, side effects, and risk. Presenting 2-3 options with a recommendation lets the user decide on the acceptable change footprint before any implementation begins.