root-cause

Analyze bugs and test failures to document root causes and potential fixes.

2.3k|331|Updated Jun 3, 2024
One-click install
npx skills add https://github.com/crbnos/carbon --skill root-cause-crbnos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: root-cause
Source: https://github.com/crbnos/carbon/tree/main/.ai/skills/root-cause
Command: npx skills add https://github.com/crbnos/carbon --skill root-cause-crbnos

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines root cause analysis for bugs, test failures, and unexpected behaviors by providing a structured process for identifying and documenting the underlying issues.

Core Features & Use Cases

  • Read-Only Analysis: Ensures no edits, commits, or state changes, focusing solely on understanding the problem.
  • Evidence-Based Briefs: Delivers concise briefs outlining the root cause, files to change, approach, and risks.
  • Use Case: Before proposing a fix, use this Skill to analyze a reported bug and produce a detailed brief that guides the resolution process.

Quick Start

Analyze the root cause of a bug using the 'root-cause' skill.

Frequently Asked Questions about root-cause

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

FAQPage Schema
How do I identify the root cause of a bug or test failure?

Root cause analysis for unexpected software behavior is conducted through read-only codebase examination, which strictly avoids making edits or commits and outputs a detailed brief outlining the underlying issue and potential fixes.

What is the best way to document root cause analysis findings for software development?

The best way to document root cause analysis findings is by generating evidence-based briefs that concisely outline the root cause, identify files to change, detail the approach, and highlight potential risks for the resolution process.

Can I analyze unexpected software behaviors without modifying the codebase?

Yes, you can analyze unexpected behaviors without modifying the codebase by using a read-only analysis process that focuses solely on understanding the problem while ensuring no edits, commits, or state changes occur in the environment.

Does root cause analysis provide specific files to change when fixing a bug?

Yes, root cause analysis provides specific files to change by delivering concise evidence-based briefs that outline the underlying root cause, the exact files needing modification, the approach, and associated risks.

When do I need a structured root cause analysis process for issue tracking?

You need a structured root cause analysis process for issue tracking when you require precise, detailed evidence-based findings to understand a reported bug or test failure before proposing and implementing a fix.