bmad-os-root-cause-analysis

Name: bmad-os-root-cause-analysis
Availability: InStock
Author: GenEd

Analyze bug-fix commits to produce structured root cause analysis reports.

Updated Mar 30, 2026

Search Tags:#git #bug fix #root cause analysis #github #postmortem #incident investigation #blame

Ready to run

npx skills add https://github.com/GenEducation/GenedUIProject --skill bmad-os-root-cause-analysis-geneducation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bmad-os-root-cause-analysis
Source: https://github.com/GenEducation/GenedUIProject/tree/main/.gemini/skills/bmad-os-root-cause-analysis
Command: npx skills add https://github.com/GenEducation/GenedUIProject --skill bmad-os-root-cause-analysis-geneducation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns a bug fix into a clear root cause analysis so you can understand what broke, why it broke, and how to stop it from happening again.

Core Features & Use Cases

Bug-Fix Investigation: Traces a fix commit or pull request back to the change that introduced the defect.
Evidence-Driven Reporting: Uses git history, blame, issue discussion, and repository guardrails to build a factual timeline.
Preventive Action Planning: Produces a structured RCA with root cause, contributing factors, and concrete corrective actions.
Use Case: A production incident is patched, and you need a concise report that identifies the introducing commit, the responsible author, detection latency, and what tests or checks failed to catch it.

Quick Start

Ask this Skill to analyze a bug-fix commit, pull request, or issue description and it will produce a structured root cause analysis report with evidence, timeline, and prevention recommendations.

Frequently Asked Questions about bmad-os-root-cause-analysis

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

FAQPage Schema

How do I do a root cause analysis on a git bug-fix commit?▼

Root cause analysis on a git bug-fix commit traces the fix back to the introducing change using git history and blame. This Skill generates a structured RCA report detailing the timeline, contributing factors, and preventive actions.

What is the best way to write a postmortem for a production incident?▼

Writing a postmortem for a production incident requires identifying the root cause, detection latency, and failed guardrails. This Skill analyzes the fix commit and issue discussion to produce a factual, evidence-driven incident investigation report.

Do I need GitHub CLI and a local git repository to investigate a bug?▼

Yes, investigating a bug requires GitHub CLI access and a local git repository. These dependencies allow the Skill to inspect historical commits, pull request discussions, and blame information to reconstruct the defect timeline.

Can I use git blame to identify who introduced a defect?▼

Yes, git blame identifies the specific commit and author who introduced a defect. This Skill uses blame data alongside issue discussions and repository guardrails to assess detection gaps and build a complete RCA timeline.

How do I find what tests failed to catch a bug in my pull request?▼

Finding failed tests involves analyzing repository guardrails and historical commit evidence. This Skill evaluates detection gaps in your pull request to determine which checks failed to prevent the bug from merging.