skills.rest
liuzhengdongfortest
liuzhengdongfortestCOMMUNITY
Explore all skills by this author →
GitHub

cs-issue-analyze

Trace code paths to identify root causes and propose 2-3 fixes.

1.1k|82|Updated Apr 12, 2026
Search Tags:#debugging#risk-assessment#code-analysis#triage#root-cause#issue-management#codestable
One-click install
npx skills add https://github.com/liuzhengdongfortest/CodeStable --skill cs-issue-analyze
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cs-issue-analyze
Source: https://github.com/liuzhengdongfortest/CodeStable/tree/main/cs-issue-analyze
Command: npx skills add https://github.com/liuzhengdongfortest/CodeStable --skill cs-issue-analyze

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides teams to locate root causes of bugs by reading issue reports and code paths, and to present 2-3 actionable repair options for decision-makers without modifying the code in this stage.

Core Features & Use Cases

  • Locate root causes by tracing code paths against issue reports.
  • Reconstruct failure paths and assess risk to guide remediation.
  • Propose 2-3 concrete fixes with rationale for TA decision-making.

Quick Start

Process the confirmed {slug}-report.md to locate the root cause and propose 2-3 fixes for TA review.

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 by tracing code paths from an issue report?▼

To find the root cause of a bug, you can trace execution paths against your issue reports to reconstruct failure paths and assess module-level risk. This identifies the exact fault location without modifying the codebase.

What is the best way to provide actionable repair options for a confirmed bug report?▼

Providing actionable repair options for a bug report involves parsing the issue context and tracing execution paths to output 2-3 concrete fixes with rationale, enabling decision-makers to select a remediation strategy.

Can I analyze code paths and assess risk across multiple modules for issue management?▼

Yes, you can analyze code paths and assess risk across multiple modules for issue management by reading issue reports and related artifacts. This enables thorough assessment across files to locate the fault accurately.

Do I need a specific issue report format to start code analysis and triage?▼

You need a confirmed issue report described in a {slug}-report.md file along with related codestable artifacts. These provide the necessary context to parse the issue and trace execution paths.

Why does root-cause analysis stop at proposing fixes instead of modifying the code directly?▼

Root-cause analysis stops at proposing fixes to separate fault identification from implementation. It delivers a structured analysis with 2-3 recommended fixes for TA review, ensuring decision-makers control code modifications.

Related Skills

Explore More Software Engineering Skills→
liuzhengdongfortestliuzhengdongfortest
1.1k

easysdd-issue-analyze

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

Community
Advanced
tomguntomgun

fixing-bugs

Reproduce bugs with regression tests and apply minimal root-cause fixes.

Community
Intermediate
grafanagrafana
31

gitnexus-impact-analysis

Map code change dependents and affected execution paths with GitNexus.

Official
Advanced
lee-tolee-to
56

aif-fix

Guide developers through structured bug fixes from issue intake to patch submission.

Community
Advanced