Claude Skill: Incident Review

Resource overview Purpose
• Skill for turning an outage or bug into timeline, impact, root cause, contributing factors, and follow-up actions.

Recommended SKILL.md contents
• Trigger description explaining when Claude should use the skill.
• Step-by-step procedure for the workflow.
• Required checks before edits or publication.
• Verification command or manual acceptance checklist.
• Links to supporting examples, scripts, or templates when the workflow needs them.

What it helps you do

Use this skill because it creates practical incident learning without blame or vague action items.

Skills load their full instructions only when used, which keeps normal session context smaller.

A reusable `SKILL.md` gives teams a versioned workflow instead of repeated ad hoc prompts.

Best fit users

engineering managers, SRE teams, support teams, and product owners.

Teams standardizing AI-assisted delivery across multiple repositories.

Builders who want Claude to apply consistent procedures without repasting instructions.

What to know first

incident timeline, logs, alerts, deployment events, customer impact, and mitigation notes.

A skill directory such as `.claude/skills/<skill-name>/SKILL.md` or `~/.claude/skills/<skill-name>/SKILL.md`.

A concise frontmatter description so Claude can decide when to load the skill.

Environment needed

access to sanitized logs or reports plus a team incident template.

Claude Code skill support and access to the files or commands the workflow needs.

Any external APIs, MCP servers, credentials, or local runtimes required by the specific workflow.