bug-analysis

Organize bug triage, root-cause analysis, and remediation guidance.

14|11|Updated Dec 1, 2025

Search Tags:#templates #documentation #investigation #triage #analyze #root-cause #bug

Ready to run

npx skills add https://github.com/DauQuangThanh/hanoi-rainbow --skill bug-analysis

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bug-analysis
Source: https://github.com/DauQuangThanh/hanoi-rainbow/tree/main/skills/bug-analysis
Command: npx skills add https://github.com/DauQuangThanh/hanoi-rainbow --skill bug-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill provides structured bug analysis workflows to identify root causes, assess impact, and generate actionable fixes to accelerate resolution.

Core Features & Use Cases

Triage & classification: Standardized severity, type, and priority assessment to speed up prioritization.
Root Cause Analysis (RCA): Step-by-step investigation with evidence collection and hypothesis testing.
Remediation guidance: Structured fix plans, testing requirements, and prevention measures to prevent recurrence.
Use Case: When a bug is reported, teams follow the workflow to reproduce, diagnose, and implement a durable fix.

Quick Start

Describe the observed symptoms, reproduce the bug, and log steps, evidence, and environment details to begin analysis.

Frequently Asked Questions about bug-analysis

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

FAQPage Schema

How do I perform root-cause analysis for a crash report or error log?▼

Root-cause analysis for crash reports involves step-by-step investigation with evidence collection, hypothesis testing, and impact assessment to identify the underlying issue. This process accelerates resolution by providing a structured workflow to reproduce, diagnose, and document the bug.

What is the best way to triage bugs and classify severity for feature regressions?▼

Bug triage uses standardized severity, type, and priority assessment to speed up prioritization for feature regressions. It organizes reported issues into clear classifications, allowing teams to quickly determine impact and allocate resources effectively.

How do I document bug remediation and prevention measures after diagnosis?▼

Bug remediation documentation requires structured fix plans, testing requirements, and prevention measures to prevent recurrence. It ensures that after diagnosing the root cause, teams implement durable fixes with proper test planning and future safeguards.

Can I investigate performance bugs across different environments and codebases?▼

Yes, investigating performance bugs across environments and codebases is supported by applying structured collection of evidence and impact assessment. The workflow adapts to various teams and environments to ensure consistent evidence gathering and diagnosis.

What information do I need to start analyzing a reported bug?▼

To start analyzing a reported bug, you need to describe the observed symptoms, reproduce the bug, and log the reproduction steps, evidence, and environment details. This initial evidence collection is necessary to begin the structured investigation workflow.