create-retrospective

Generate incident retrospectives from session logs and Git history, then publish to GitHub Discussions.

2|Updated Feb 23, 2026

Search Tags:#automation #documentation #github #retrospective #post-mortem #incident management

Ready to run

npx skills add https://github.com/vultuk/coding-agents --skill create-retrospective

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-retrospective
Source: https://github.com/vultuk/coding-agents/tree/main/skills/create-retrospective
Command: npx skills add https://github.com/vultuk/coding-agents --skill create-retrospective

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the creation and publication of detailed incident retrospectives, transforming raw incident data into a polished, shareable format.

Core Features & Use Cases

Automated Evidence Gathering: Collects data from session actions, logs, Git history, and GitHub issues/PRs.
Structured Retrospective Drafting: Uses a template to generate factual and concise retrospective reports.
Direct Publishing: Publishes the drafted retrospective to GitHub Discussions.
Use Case: After a critical production incident, use this Skill to automatically gather all relevant information, draft a comprehensive retrospective, and post it to the 'Retrospectives' category on GitHub.

Quick Start

Use the create-retrospective skill to draft and publish a retrospective for the recent outage.

Frequently Asked Questions about create-retrospective

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

FAQPage Schema

How do I automate incident retrospectives for GitHub?▼

To automate incident retrospectives, this Skill collects evidence from session actions, logs, Git history, and GitHub artifacts, then drafts a factual report using a predefined template before publishing it directly to GitHub Discussions.

Does creating an automated post-mortem require linking issues and PRs?▼

Creating an automated post-mortem involves resolving linked issues and PRs to establish the incident scope. The Skill gathers this GitHub data alongside session logs to draft a comprehensive and factual retrospective report.

Can I publish a retrospective directly to GitHub Discussions?▼

Yes, you can publish a retrospective directly to GitHub Discussions. The Skill drafts the structured report from collected evidence and automatically posts it to the Retrospectives category on your repository.

Do I need the gh CLI to generate incident reports?▼

Yes, you need the gh CLI installed to generate incident reports. This Skill relies on the gh dependency to interact with GitHub, resolve linked issues and PRs, and publish the final retrospective to GitHub Discussions.

What is the best way to document a production outage using Git history?▼

The best way to document a production outage is to automate evidence gathering from Git history and logs. This Skill resolves linked GitHub artifacts to establish incident scope and drafts a concise report using a predefined template.