skills.rest
duronext
duronextOFFICIAL
Explore all skills by this author →
WebsiteGitHub

postmortem

Analyze merged pull requests to catalog lessons learned and recommend skill updates.

15|1|Updated Mar 29, 2026
Search Tags:#skills#retrospective#postmortem#specialists#pr-review#lessons-learned
One-click install
npx skills add https://github.com/duronext/jig --skill postmortem-duronext
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: postmortem
Source: https://github.com/duronext/jig/tree/main/core/skills/postmortem
Command: npx skills add https://github.com/duronext/jig --skill postmortem-duronext

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After a PR is merged, teams often miss systematic learnings. This Skill structures post-merge reflections to identify gaps in skills and specialists and to apply targeted improvements.

Core Features & Use Cases

  • Collect reviewer feedback and highlight recurring patterns across PRs.
  • Cross-reference insights with existing skills and specialists to close coverage gaps.
  • Produce a ready-to-commit plan with recommended updates to skill/specification files.

Quick Start

Run a postmortem on a merged PR to generate an actionable lessons-learned report and an improvement plan.

Frequently Asked Questions about postmortem

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

FAQPage Schema
How do I extract lessons learned from merged pull requests?▼

Run a postmortem on merged pull requests to catalog lessons learned by analyzing PR metadata, comments, and existing skill references. This surfaces reviewer feedback patterns and coverage gaps to drive targeted improvements.

What is a PR postmortem workflow for software engineering teams?▼

A PR postmortem workflow systematically identifies gaps in skills and specialists after a merge. It structures post-merge reflections by cross-referencing reviewer feedback with existing skills to close coverage gaps and generate concrete improvement plans.

How do I turn recurring reviewer feedback into concrete skill improvements?▼

Turn recurring reviewer feedback into concrete improvements by collecting comments across PRs and cross-referencing insights with existing skills. This closes coverage gaps and produces a ready-to-commit plan with recommended updates to specification files.

Can I use a retrospective process to update specification files across multiple projects?▼

Yes, you can apply a retrospective process across projects to update specification files. It analyzes PR metadata and existing skill references to output a recommended set of updates and a structured follow-up plan for multiple projects.

What is the best way to identify coverage gaps in specialists after a merge?▼

The best way to identify coverage gaps in specialists is to cross-reference reviewer feedback patterns with existing skills after a merge. This structured analysis surfaces missing capabilities and outputs a concrete plan for targeted improvements.

Related Skills

Explore More Software Engineering Skills→
openshift-engopenshift-eng

CodeRabbit Rules from PR Reviews - Fetch Comments

Fetch and filter human PR review comments from GitHub repos into structured JSON.

Official
Intermediate
Tx1207Tx1207
5

skill-improver

Apply prioritized improvement plans to Claude Skills with conflict resolution and backups.

Community
Advanced
diiviikk5diiviikk5

review

Analyze PR diffs for SQL safety, LLM trust boundaries, and structural issues.

Community
Advanced
TraitomeTraitome
1

check-skill

Validate oxo-call skill.md files against local and online documentation.

Official
Advanced