bmad-os-root-cause-analysis

Correlate git history and PR metadata to generate root cause analysis reports.

8|2|Updated Feb 1, 2026

Search Tags:#git #debugging #root cause analysis #github #post-mortem #rca

Ready to run

npx skills add https://github.com/bmad-code-org/bmad-utility-skills --skill bmad-os-root-cause-analysis-bmad-code-org

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bmad-os-root-cause-analysis
Source: https://github.com/bmad-code-org/bmad-utility-skills/tree/main/skills/bmad-os-root-cause-analysis
Command: npx skills add https://github.com/bmad-code-org/bmad-utility-skills --skill bmad-os-root-cause-analysis-bmad-code-org

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh.

What problem does it solve?

This skill automates the labor-intensive process of investigating bug fixes, identifying the original source of the defect, and generating a structured post-mortem report.

Core Features & Use Cases

Automated RCA Generation: Automatically gathers diffs, git logs, and PR discussions to perform a 5 Whys analysis.
Guardrail Evaluation: Audits repository configuration and CI/CD workflows to identify why existing tests or linters failed to catch the bug.
Use Case: When a critical bug is patched, use this skill to generate a professional RCA report that identifies the root cause, the detection latency, and actionable preventive measures for the team.

Quick Start

Run the bmad-os-root-cause-analysis skill by providing the commit SHA or PR number of the bug fix you want to investigate.

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 automate root cause analysis for a git bug fix?▼

Automating root cause analysis for a git bug fix involves correlating commit history, PR metadata, and repository configuration to identify systemic failures. This skill automatically gathers diffs and logs to perform a 5 Whys analysis and generate a markdown report.

How does a blameless post-mortem analysis work with GitHub PRs?▼

A blameless post-mortem analysis works by examining PR discussions and git history without assigning individual fault. The skill correlates this metadata to evaluate detection latency and identify why existing CI/CD guardrails failed to catch the defect.

Can I use GitHub CLI to generate RCA reports for software bugs?▼

Yes, you can use GitHub CLI to generate RCA reports by providing a commit SHA or PR number. The skill requires GitHub CLI authentication and local git repository access to execute diagnostic commands and produce the analysis.

What's the best way to find why CI tests failed to catch a bug?▼

The best way to find why CI tests failed is through guardrail evaluation, which audits repository configuration and CI/CD workflows. This skill identifies gaps in existing tests or linters that allowed the defect to slip through.

Do I need local git repository access to perform automated RCA?▼

Yes, local git repository access is required to perform automated RCA. The skill needs local access to execute git diagnostic commands, gather diffs, and read repository configuration alongside GitHub CLI authentication.