bug-fix-review

Analyze bug reports and code changes to generate root cause and risk assessments.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/taptap/agents-plugins --skill bug-fix-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bug-fix-review
Source: https://github.com/taptap/agents-plugins/tree/main/plugins/test/skills/bug-fix-review
Command: npx skills add https://github.com/taptap/agents-plugins --skill bug-fix-review

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about bug-fix-review

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

FAQPage Schema
How do I analyze a bug fix and assess regression risk from an MR link?

To analyze a bug fix and assess regression risk, provide a Feishu bug link along with code diffs or MR links. The workflow fetches bug descriptions, parses code changes, and outputs structured files for root cause analysis and risk mitigation.

What is root cause analysis for code diffs and how does it work?

Root cause analysis for code diffs breaks down bug descriptions and code changes to identify likely causes and affected files. It evaluates fix completeness and enumerates potential regressions to produce a confidence-scored report.

Can I generate JSON and markdown artifacts for automated code review?

Yes, you can generate JSON and markdown artifacts for automated code review. The process emits bug_fix_analysis.json, risk_assessment.json, and code_analysis.md files to integrate with downstream pipelines and reviewer checklists.

Does the bug-fix-review skill work with local diff files and Feishu bug links?

The bug-fix-review skill accepts local diff files and Feishu bug links as inputs. It fetches supplemental bug descriptions and parses diffs to produce a formal residual risk assessment and completeness verdict.

What are the limitations of using bug-fix-review for code analysis?

The primary limitation is that bug-fix-review is deprecated, with its bug scenario merged into change-analysis. You should use the change-analysis skill for active workflows to run full root cause analysis and risk assessment.