postmortem

Analyze Git fix commits and generate structured postmortem reports.

6|1|Updated Jan 3, 2026
One-click install
npx skills add https://github.com/peeka-project/peeka --skill postmortem-peeka-project
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: postmortem
Source: https://github.com/peeka-project/peeka/tree/main/.agents/skills/postmortem
Command: npx skills add https://github.com/peeka-project/peeka --skill postmortem-peeka-project

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the generation of postmortem reports by analyzing fix commits, reviewing existing topics, selecting representative incidents, and organizing them into curated reports.

Core Features & Use Cases

  • Postmortem Report Generation: Analyze fix commits and generate reports on issues that were fixed in previous versions.
  • Incident Analysis: Analyze incidents to identify root causes, impact, and potential prevention measures.
  • Topic Organization: Organize incidents by topic, providing a structured way to understand recurring patterns.
  • Use Case: Imagine you have a list of fix commits in your Git repository. Use this Skill to automatically generate postmortem reports for those commits, which will help you analyze and understand the incidents that occurred in previous versions.

Quick Start

Use the postmortem skill to generate a report for commits between tags 'v0.1.5' and 'latest'.

Frequently Asked Questions about postmortem

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

FAQPage Schema
How do I automate postmortem report generation from Git commits?

This Skill automates postmortem report generation by analyzing fix commits within a Git repository, identifying incidents, and organizing them into structured reports detailing root causes, impacts, and prevention measures.

What is incident analysis and how does it work with version control?

Incident analysis works by examining fix commits in a Git repository to identify root causes, impact, and potential prevention measures, organizing incidents by topic to reveal recurring patterns in previous versions.

How do I generate a postmortem report for commits between two Git tags?

To generate a postmortem report for commits between Git tags, specify a tag range like 'v0.1.5' and 'latest'; the Skill filters fix commits within that scope and produces a structured incident analysis report.

Do I need Git to analyze incidents and identify root causes?

Yes, you need Git to analyze incidents and identify root causes using this Skill, as it relies on Git version control to review commit messages, handle issue references, and filter fix commits for report generation.

Can I organize incidents by topic to find recurring patterns in fix commits?

Yes, you can organize incidents by topic to find recurring patterns. The Skill categorizes fix commits by scope and issue references, structuring the postmortem report to help you understand recurring problems in previous versions.

What is the best way to analyze fix commits in previous software versions?

The best way to analyze fix commits in previous software versions is to automate the review process; this Skill selects representative incidents from Git history and generates curated postmortem reports for structured analysis.