skills.rest
leifericf
leifericfCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

review-incident

Execute a structured incident review to identify contributing factors and define action items.

5|3|Updated Mar 20, 2026
Search Tags:#system reliability#incident review#actionable insights#blameless post-mortem#post-incident analysis
One-click install
npx skills add https://github.com/leifericf/agentic-sdk --skill review-incident
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-incident
Source: https://github.com/leifericf/agentic-sdk/tree/main/skills/review-incident
Command: npx skills add https://github.com/leifericf/agentic-sdk --skill review-incident

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill aids in running blameless incident reviews, promoting learning and preventing recurrence, thus enhancing system reliability and team morale.

Core Features & Use Cases

  • Blameless Review: Facilitates a factual, empathetic, and thorough review process.
  • Timeline Construction: Assists in building a chronological timeline of events.
  • Response Analysis: Documents and reviews the response to the incident.
  • Action Item Definition: Defines actionable items to prevent future incidents.
  • Follow-Up Verification: Ensures the effectiveness of the implemented actions.
  • Use Case: After an incident, use this Skill to conduct a review and generate a comprehensive report for continuous improvement.

Quick Start

Run the 'review-incident' Skill to initiate a blameless incident review.

Frequently Asked Questions about review-incident

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

FAQPage Schema
What is a blameless post-mortem in incident review?▼

A blameless post-mortem is an incident review process focusing on identifying contributing factors rather than assigning fault. It promotes factual analysis of system reliability failures to generate actionable insights and prevent recurrence.

How do I conduct a post-incident analysis for system reliability?▼

To conduct post-incident analysis, execute a structured review process capturing impact, detection, response, and communication. This generates a comprehensive report defining actionable items for continuous improvement.

What information do I need to provide for an incident review?▼

You need to provide input on impact, detection, response, and communication. Supplying these details allows the review process to construct a chronological timeline and define action items.

How does an incident review help prevent future system outages?▼

An incident review prevents future outages by defining actionable items and verifying their effectiveness through follow-up. This structured process identifies contributing factors to enhance system reliability.

What is the best way to document an incident timeline for post-incident analysis?▼

The best way to document an incident timeline is using a structured review process that constructs a chronological sequence of events. This factual timeline supports response analysis and action item definition.

Can I use this incident review process for IT operations workflows?▼

Yes, this incident review process applies to post-incident analysis workflows in software development and IT operations. It facilitates factual, empathetic reviews to enhance team morale and system reliability.

Related Skills

Explore More Software Engineering Skills→
dralgorhythmdralgorhythm
111

incident-management

Coordinate production incident response through detection, triage, investigation, mitigation, resolution, and post-mortem analysis.

Community
Advanced
Yukine5377Yukine5377

bmad-retrospective

Facilitate structured epic retrospectives to capture lessons and plan improvements.

Community
Advanced
hotaqhotaq

trace

Display chronological agent flow timelines and aggregate session summaries.

Community
Intermediate
meaganewallermeaganewaller
3

root-cause

Perform structured root cause analysis using 5-Whys methodology.

Community
Advanced