What problem does it solve?
Provides a structured workflow to analyze bug reports and associated code changes, determine root cause, evaluate fix completeness, and produce a formal residual risk assessment so teams can avoid regressions and unsafe fixes. Note: this skill is deprecated and its Bug scenario has been merged into change-analysis; use change-analysis for active workflows.
Core Features & Use Cases
- Root cause analysis: break down bug descriptions and diffs to identify likely causes and affected files.
- Fix completeness & side-effect evaluation: assess whether proposed changes fully address the bug and enumerate potential regressions.
- Structured outputs for automation: emit bug_fix_analysis.json, risk_assessment.json, and code_analysis.md to integrate with downstream pipelines and reviewer checklists.
- Use case: given a Feishu bug link plus MR links or local diff files, generate a confidence-scored root cause report, a completeness verdict, and actionable risk mitigation tasks.
Quick Start
Open the change-analysis skill's Bug scenario and provide the bug link along with the code diff or MR links to run a full root cause analysis and risk assessment.