rollback-postmortem

Generate post-mortem reports for rolled-back features and update GitHub issues.

3|Updated May 20, 2026
One-click install
npx skills add https://github.com/iampawan/Manifest --skill rollback-postmortem
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rollback-postmortem
Source: https://github.com/iampawan/Manifest/tree/main/skills/rollback-postmortem
Command: npx skills add https://github.com/iampawan/Manifest --skill rollback-postmortem

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

After a feature rollback, it can be difficult to document what happened and track necessary follow-up actions. This skill automates the post-mortem process, creating detailed reports, and updating issue tracking systems.

Core Features & Use Cases

  • Post-mortem Documentation: Automatically generates blameless post-mortem reports based on feature timelines and guard reports.
  • Slack Notifications: Posts rollback summaries and action items to Slack for team awareness.
  • Issue Tracking: Re-opens and updates issue tracking systems to ensure the rollback process is followed-up.
  • Use Case: Following a failed feature launch, this skill creates a comprehensive report that identifies issues and outlines next steps without finger-pointing.

Quick Start

Trigger a post-mortem by running /postmortem <ID> where <ID> is the unique identifier for the rolled-back feature.

Frequently Asked Questions about rollback-postmortem

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

FAQPage Schema
How do I automate post-mortem documentation after a feature rollback?

Automating post-mortem documentation after a feature rollback involves generating blameless reports from feature timelines and guard reports. This skill creates detailed summaries and shares them with your team automatically.

Can I integrate Sentry error reporting with Slack for rollback notifications?

Yes, integrating Sentry error reporting with Slack for rollback notifications is supported. The skill pulls error data from Sentry and posts rollback summaries along with action items directly to Slack channels.

How do I track rolled-back features using the GitHub Issues API?

Tracking rolled-back features using the GitHub Issues API involves re-opening and updating issue statuses automatically. This ensures the rollback process is properly followed up on within your existing development tracking system.

What is a blameless post-mortem report for a failed feature launch?

A blameless post-mortem report for a failed feature launch identifies issues and outlines next steps without finger-pointing. It captures lessons learned from the feature timeline to prevent future occurrences.

Do I need any external dependencies to run automated issue tracking for rollbacks?

No external dependencies are required to run automated issue tracking for rollbacks. The skill operates independently using internal scripts and references to integrate with your existing Sentry, Slack, and GitHub environments.

What is the best way to trigger a post-mortem for a rolled-back feature?

The best way to trigger a post-mortem for a rolled-back feature is by executing a simple command with the feature's unique identifier. This initializes the automated reporting and issue tracking process immediately.