BUG 定位与修复

Diagnose and repair software bugs with root-cause analysis and validation.

Updated Sep 5, 2021
One-click install
npx skills add https://github.com/a747895159/spring-cloud-study-alibaba --skill bug-a747895159
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: BUG 定位与修复
Source: https://github.com/a747895159/spring-cloud-study-alibaba/tree/main/.agent/skills/bug-diagnosis
Command: npx skills add https://github.com/a747895159/spring-cloud-study-alibaba --skill bug-a747895159

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

系统化地定位和修复 BUG,确保问题彻底解决且不引入新问题

Core Features & Use Cases

  • 诊断流程
  • 常见 BUG 类型
  • 定位技巧
  • 根因分析
  • 修复模板与验证
  • 验证与预防

Quick Start

按诊断流程逐步定位并修复问题,确保修复彻底且不引入新问题。

Frequently Asked Questions about BUG 定位与修复

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

FAQPage Schema
How do I systematically locate and fix bugs without introducing new issues?

Systematically locating and fixing bugs requires following a structured diagnostic flow, applying root-cause analysis, and using standardized repair templates with thorough validation. This ensures durable fixes without introducing new issues across codebases.

What is root-cause analysis and how does it help in bug diagnosis?

Root-cause analysis in bug diagnosis identifies the fundamental origin of a defect rather than just treating symptoms. By applying structured templates and thorough logging, it ensures issues are resolved permanently and prevents recurring failures.

How do I verify a bug fix is durable in a production environment?

To verify a bug fix is durable in a production environment, apply structured validation steps and thorough logging during triage. This confirms the repair resolved the original issue completely without introducing regressions or new defects.

Can I use this structured debugging approach for triage sessions across different codebases?

Yes, you can use this structured debugging approach for triage sessions across different codebases. It applies systematic diagnosis and root-cause analysis techniques universally, ensuring consistent repair verification regardless of the specific software environment.

What are the limitations of fixing bugs without structured templates and logging?

Fixing bugs without structured templates and logging limits reproducibility and root-cause analysis accuracy. It increases the risk of incomplete repairs or introducing new issues, bypassing the validation steps needed to guarantee durable fixes.