Emergency Release Workflow

When production is on fire and you need to ship a fix right now, this gives you a structured way to move fast without breaking everything else. It walks you through assessing whether something truly needs the emergency track (security CVEs, service outages, payment failures), then handles the expedited PR process, deployment verification, and post-incident writeup. Created by bobmatnyc with 140 installs and passing security audits from Gen Agent Trust Hub, Socket, and Snyk. The kind of thing you hope you never need but will be grateful to have when your monitoring starts screaming at 2am. Beats scrambling to remember your company's emergency runbook while half the team is pinging Slack.

skills.sh installs: 328
GitHub stars: 79
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add bobmatnyc/claude-mpm-skills --skill emergency-release-workflow --agent claude-code

Installs into .claude/skills of the current project.

Files

Emergency Release Workflow Skill

Summary

Fast-track workflow for critical production issues requiring immediate deployment. Covers urgency assessment, expedited PR process, deployment verification, and post-incident analysis.

When to Use

Critical production bugs affecting users
Security vulnerabilities (CVEs)
Urgent business requirements
Data integrity issues
Service outages
Payment processing failures

Urgency Assessment

Priority Levels

Level	Type	Response Time	Deployment	Example
P0	Security vulnerability	< 2 hours	Immediate to production	Auth bypass, data leak, active exploit
P1	Production down	< 4 hours	Same day	App crash, complete feature failure, payment down
P2	Major bug	< 24 hours	Next business day	Critical feature broken, significant user impact
P3	Business critical	< 48 hours	Scheduled release	Marketing campaign blocker, partner deadline