Incident Followup Audit
技能 已验证 活跃Audits post-incident engineering follow-through after a sev or incident to verify whether the durable follow-up happened: regression tests, monitors, docs, runbooks, ownership updates, tickets, rollback learnings, and remaining backlog. Use when a user asks whether incident follow-up is complete, what still needs to be done after a postmortem, or how to close the engineering loop. Do NOT use for live incident response, root-cause analysis, or a generic bug hunt unrelated to an incident.
To provide a structured audit of post-incident engineering follow-through, ensuring that all necessary follow-up actions are completed and closing the engineering loop after an incident.
功能
- Audits post-incident engineering follow-through
- Verifies durable follow-up actions
- Identifies missing or incomplete work
- Ranks remaining backlog by risk and impact
- Anchors audit to specific incident identifiers
使用场景
- Audit postmortem follow-through after a sev or production incident
- Check whether regression tests, monitors, runbooks, or docs were added
- See whether ownership, tickets, or rollback learnings were captured
- Review what is still left to do before an incident is considered fully closed
非目标
- Live incident response or war-room triage
- Root-cause analysis of the incident itself
- Generic code review or bug hunting unrelated to an incident
- Broad cleanup work not tied to a concrete incident or postmortem
Practical Utility
- info:Usage examplesThe SKILL.md outlines the desired output structure and evidence types but does not provide concrete, copy-pasteable end-to-end examples of invocations and their claimed outputs.
安装
/plugin install swe-skills@ckorhonen-swe-skills质量评分
已验证类似扩展
Ship Gate
100Pre-production audit that scans a codebase for security, database, deployment, code quality, AI/LLM, dependency, frontend, and observability issues. Intercepts deploy commands and blocks until critical items pass. Stack-agnostic. Use for "run ship gate", "am I ready to ship", "pre-launch audit", "can I deploy", "push to production", "go live checklist", "preflight check". Not for CI/CD setup or infra provisioning.
Incident Response
100Manage active production incidents through detection, triage, mitigation, communication, and resolution with structured roles and decision-making. Use this skill whenever the user has an active incident, a production issue, a service outage, a security incident, or needs to plan incident response procedures. Triggers on incident response, production incident, outage, service down, site down, P0, P1, severity, downtime, on-call, incident commander, status page, postmortem prep. Also triggers when something is actively broken in production and the user is figuring out what to do.
Ops Fires
100Production incidents dashboard. Reads ECS health, Sentry errors, CI failures. Offers to dispatch fix agents for active fires.
After Action Report
100Run a structured after-action review (postmortem, retrospective) on a launch, incident, or completed project to capture timeline, root cause analysis, contributing factors, and actionable lessons. Use this skill whenever the user wants to run a postmortem, retrospective, AAR, or after-action review on any past event. Triggers on after-action report, AAR, postmortem, retrospective, retro, post-incident review, what went well what didn't, lessons learned, blameless postmortem, root cause analysis, RCA, five whys. Also triggers when the user has just shipped something or just resolved an incident and wants to capture learnings.
SRE Engineer
98Defines service level objectives, creates error budget policies, designs incident response procedures, develops capacity models, and produces monitoring configurations and automation scripts for production systems. Use when defining SLIs/SLOs, managing error budgets, building reliable systems at scale, incident management, chaos engineering, toil reduction, or capacity planning.
Incident Commander
98Incident Commander Skill