premortem

Review commits to identify potential incidents from unguarded gaps.

45|13|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/rakovi4/continue-framework --skill premortem-rakovi4
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: premortem
Source: https://github.com/rakovi4/continue-framework/tree/main/.claude/skills/premortem
Command: npx skills add https://github.com/rakovi4/continue-framework --skill premortem-rakovi4

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps users identify potential issues that could arise from recently committed work units, ensuring that unguarded gaps are addressed before they become significant problems.

Core Features & Use Cases

  • Post-Commit Review: Analyzes the latest commit or specified range of commits to surface unguarded gaps.
  • Gap Identification: Assesses the impact of the shipped work unit and identifies potential incidents.
  • Use Case: After a work unit is committed, use /premortem to imagine the incident it could cause and uncover any unaddressed issues.

Quick Start

Run the command '/premortem' to review the latest work-unit commit.

Frequently Asked Questions about premortem

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

FAQPage Schema
How do I analyze a commit range to identify potential incidents from shipped work units?

Post-commit review analyzes your commit range using diff analysis and the work unit's description context to identify potential incidents from shipped work units, ensuring unguarded gaps are addressed before they escalate.

What is a post-commit review for code quality and incident analysis?

Post-commit review is the process of inspecting committed code to assess the impact of a shipped work unit. It identifies unguarded gaps and imagines the potential incidents a commit could cause to proactively address issues.

Can I inspect a specific commit for unguarded gaps after shipping a work unit?

Yes, you can inspect a specific commit or the latest commit range. The review utilizes diff analysis and context from the work unit's description to surface unguarded gaps and assess the impact of the shipped work unit.

How do I check committed code for potential incidents before they become significant problems?

You run a post-commit review to identify potential issues from recently committed work units. This assesses the impact of the shipped work unit and uncovers unaddressed issues, ensuring unguarded gaps are addressed proactively.

Does post-commit review work with just the commit diff, or do I need the work unit description too?

Post-commit review utilizes both diff analysis and context information extracted from the work unit's description. Combining these inputs allows the review to accurately identify potential incidents and unguarded gaps from shipped work units.