Back to list
edwardmonteiro

optimizationpostmortem

by edwardmonteiro

Make Claude Skills work in other agents like Codex by adding the missing piece: a small enumerator script.

0🍴 1📅 Dec 23, 2025

SKILL.md


name: optimization.postmortem phase: optimization roles:

  • Engineering Lead
  • SRE
  • QA Lead description: Produce a post-incident analysis capturing timeline, root causes, impact, and corrective actions. variables: required:
    • name: incident_summary description: High-level summary of the incident.
    • name: impact_scope description: Systems, users, or KPIs impacted. optional:
    • name: duration description: Incident duration or timestamps.
    • name: mitigation_steps description: Steps taken during mitigation. outputs:
  • Incident timeline and contributing factors.
  • Root cause analysis with classification and detection gaps.
  • Corrective and preventive actions with owners.

Purpose

Standardize postmortem creation so engineering and reliability teams can rapidly document learnings and accountability.

Pre-run Checklist

  • ✅ Gather incident alerts, logs, and chat transcripts.
  • ✅ Confirm timeline with responders.
  • ✅ Align on severity classification and stakeholders.

Invocation Guidance

codex run --skill optimization.postmortem \
  --vars "incident_summary={{incident_summary}}" \
         "impact_scope={{impact_scope}}" \
         "duration={{duration}}" \
         "mitigation_steps={{mitigation_steps}}"

Recommended Input Attachments

  • Incident timeline exports (PagerDuty, Opsgenie, Slack).
  • Monitoring dashboards or screenshots.
  • Customer communications sent during the incident.

Claude Workflow Outline

  1. Summarize incident context, severity, impact, and timeline.
  2. Detail sequence of events with timestamps and decision points.
  3. Perform root cause analysis using techniques like 5 Whys or fishbone.
  4. Document detection gaps and monitoring improvements.
  5. Provide corrective and preventive actions with owners and deadlines.

Output Template

# Postmortem — {{incident_summary}}

## Impact & Timeline
- Severity:
- Impact Scope:
- Duration:
| Time | Event | Owner | Notes |
| --- | --- | --- | --- |

## Root Cause Analysis
- Primary Cause:
- Contributing Factors:
- Detection Gaps:

## Corrective Actions
| Action | Owner | Due Date | Status |
| --- | --- | --- | --- |

## Preventive Measures
- Monitoring Updates:
- Process Improvements:
- Follow-up Reviews:

Follow-up Actions

  • Review postmortem in reliability or engineering forums.
  • Track actions in the incident management system.
  • Schedule follow-up to verify preventive measures are in place.

Score

Total Score

60/100

Based on repository quality metrics

SKILL.md

SKILL.mdファイルが含まれている

+20
LICENSE

ライセンスが設定されている

0/10
説明文

100文字以上の説明がある

+10
人気

GitHub Stars 100以上

0/15
最近の活動

3ヶ月以内に更新がある

0/10
フォーク

10回以上フォークされている

0/5
Issue管理

オープンIssueが50未満

+5
言語

プログラミング言語が設定されている

+5
タグ

1つ以上のタグが設定されている

0/5

Reviews

💬

Reviews coming soon