skills.rest
cedricfarinazzo
cedricfarinazzoCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

merge-jira-postmortem

Generate and post structured Jira postmortems after GitHub merge.

Updated May 16, 2026
Search Tags:#automation#merge#jira#postmortem#comment#transition#merge-train
One-click install
npx skills add https://github.com/cedricfarinazzo/agile-skills --skill merge-jira-postmortem
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: merge-jira-postmortem
Source: https://github.com/cedricfarinazzo/agile-skills/tree/main/agile-merge-review/skills/merge-jira-postmortem
Command: npx skills add https://github.com/cedricfarinazzo/agile-skills --skill merge-jira-postmortem

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post-merge reviews often lack a standardized, shareable format and timely Jira updates, creating gaps in traceability and accountability.

Core Features & Use Cases

  • Automatic generation and posting of structured Jira postmortems after PR merges.
  • Support both merged mode (transition to Done) and blocked mode (no transition) while documenting root causes and lessons.
  • Cross-PR conflict detection notes and recommendations to link related issues in Jira for sprint planning.

Quick Start

Run the postmortem by invoking the /jira-postmortem trigger after a merge to generate and publish the findings.

Frequently Asked Questions about merge-jira-postmortem

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

FAQPage Schema
How do I automate Jira postmortem comments after a PR merge?▼

You can automate Jira postmortem comments by invoking the /jira-postmortem trigger after a merge, which generates structured Markdown findings and posts them directly to Jira via APIs.

Can I automatically transition Jira issues to Done when a GitHub merge train succeeds?▼

Yes, when a PR merge succeeds, the postmortem automation transitions linked Jira issues to Done automatically, while blocked PRs are documented without a status transition.

Do I need a cloudId and ticket-prefix to post merge review findings to Jira?▼

Yes, you must provide a Jira cloudId and a ticket-prefix regex in your repo's CLAUDE.md, AGENTS.md, or environment variables to identify target issues for postmortem comments.

What is the best way to document blocked PRs and cross-PR conflicts in Jira?▼

The best way is to use merge-train postmortem automation, which detects cross-PR conflicts, documents root causes for blocked PRs, and recommends linking related issues for sprint planning.

Why does my merge train postmortem skip transitioning issues to Done?▼

Postmortem automation skips the Done transition when a PR is blocked, focusing instead on documenting the root cause and lessons learned without altering the Jira issue status.

Related Skills

Explore More Software Engineering Skills→
elijahmurrayelijahmurray
2

setup-ticket-system

Configure GitHub Issues, Linear, Jira, or GitLab for issue tracking.

Community
Basic
lookatitudelookatitude
6

devops-incident-runbook

Generate Markdown incident runbooks with standard response sections for failure modes.

Community
Intermediate
BaqiF2BaqiF2
3

merge-pr

Merge GitHub Pull Requests after CI checks and code review pass.

Community
Advanced
rom-orlovichrom-orlovich

webhook-management

Manage webhook lifecycles across GitHub, Jira, Slack, and Sentry via CLI scripts.

Community
Intermediate