Individual skill
root-cause-analysis
Produce a written root-cause analysis for an incident, outage, regression, or recurring failure, with a timeline, contributing factors, and prevention actions. Use for post-mortems and "why did this happen" questions.
src/skills/builtin/root-cause-analysis/SKILL.md
Source commit 79a26efbea50aa0e351c4b5fbdfc6502fef25b8e
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Instructions only
- Last checked
- Nov 5, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 216
- Repository last updated
- Nov 5, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agentic-ai Repository topic
- ai Repository topic
- code-cli Repository topic
- code-generation Repository topic
- llms Repository topic
- ai-agents-cli Repository topic
- autonomous-agents Repository topic
- ai-coding-agent Repository topic
- ai-coding-agents Repository topic
- coding-agent Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 1,982 bytes
Read excerpt
# Root-cause analysis
The goal is a document another engineer can act on: what happened, why it was
possible, and what stops the class of failure, not just this instance.
## Gather evidence first
1. Establish the timeline from artifacts, not memory: commits (`git_log`),
deploys, config changes, alerts, logs, test runs. Timestamp everything.
2. Identify the trigger (the change or event) separately from the cause (why
the system could not tolerate it) and the contributing factors (what let
it reach users).
3. Reproduce or at least confirm the mechanism in code with file paths and
line numbers. Quote the exact lines.