Skip to main content
skill CX Codex

engineering-emergency-changes — Claude Code skill for hotfix reviews

The engineering-emergency-changes skill checks whether an urgent change merits an expedited process, then guides the agent through narrowing the fix, checking risks, and planning follow-up review.

MIT 123 installs ★ 635 updated 2026-09-29

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add agentara/skills --skill engineering-emergency-changes -a claude-code
Open on GitHub

What engineering-emergency-changes does

The skill distinguishes a genuine emergency from ordinary time pressure. It checks whether the request concerns major production impact, a serious security flaw, a legal issue, a launch at risk, or a hard external deadline. Wanting an earlier release, a Friday merge, or a soft deadline does not qualify on its own.

For a qualifying change, it guides the agent to reduce scope to the smallest fix and examine correctness, potential harm, rollback options, and the most useful available verification. Its decision template captures the reason, immediate checks, release or rollback notes, and follow-up work. Skipped routine checks need an explanation, and a normal-depth review follows once the emergency is resolved.

Install it in Claude Code with npx skills add agentara/skills --skill engineering-emergency-changes -a claude-code. A soft deadline alone does not meet the skill’s emergency criteria.

What it helps with

  • separate an emergency hotfix from routine urgency
  • narrow a proposed change to the minimum fix
  • check potential impact and rollback options
  • record skipped checks and post-incident review work

Example prompts for the agent

  • Assess whether this hotfix qualifies as an emergency change and give the reason.
  • Reduce this fix to the smallest safe change and outline immediate verification.
  • Draft an emergency decision with release risks, rollback notes, and follow-up review tasks.

How to install engineering-emergency-changes

1Skills CLI (Vercel)

npx skills add agentara/skills --skill engineering-emergency-changes -a claude-code

2Manually: put the files in place

~/.claude/skills/engineering-emergency-changes/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/engineering-emergency-changes/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about engineering-emergency-changes

How do I install engineering-emergency-changes in Claude Code?

Run npx skills add agentara/skills --skill engineering-emergency-changes -a claude-code.

What does engineering-emergency-changes do?

It evaluates whether an expedited process is justified, then helps scope a hotfix and plan verification, release, and follow-up review.

Does a soft deadline count as an emergency?

No. A desire to ship earlier, a soft deadline, or reviewers being unavailable is not sufficient by itself.

Source text

SKILL.md · MIT
---
name: engineering-emergency-changes
description: >
  Use when a code hotfix, rollback alternative, production/security/legal fix, launch blocker, or hard external deadline
  claims expedited review or relaxed process. TRIGGER on "emergency change", "hotfix", "prod incident",
  "major security hole", "must ship today", "hard deadline", "bypass review", or "fast-track this PR" for qualification
  only. DO NOT TRIGGER for ordinary urgency, soft deadlines, Friday timing, manager pressure, time-zone delay, or review
  unless emergency status is disputed.
---

# Engineering Emergency Changes

Emergency review is for rare cases where speed of the entire change matters more than normal review depth. It does not mean "skip engineering judgment"; it means narrow the change, verify the emergency, prioritize correctness, and schedule follow-up review.

Adapted from Google Engineering Practices Documentation, especially "Emergencies" and the reviewer speed guidance. Source: <https://google.github.io/eng-practices/review/emergencies.html>. License: CC-BY 3.0.

## Emergency Gate

Treat a change as an emergency only when it is a small targeted change and at least one condition is true:

- It prevents a major launch from failing when rollback is not the right option.
- It fixes a bug that is significantly affecting production users.
- It addresses a pressing legal or compliance issue.
- It closes a major security vulnerability.
- It satisfies a hard external deadline where missing it would cause contractual, legal, security, production-user, or clearly disastrous launch harm.

These are usually not emergencies by themselves:

- Wanting to launch sooner.
- A feature has taken a long time and the author wants it merged.
- Reviewers are asleep, away, or in another time zone.
- It is late Friday.
- A manager wants it done today for a soft deadline.
- The team wants to avoid normal review discomfort.

Most deadlines are soft. Do not sacrifice code health for a soft deadline.

## Emergency Workflow

1. State the emergency claim in one sentence.
2. Decide whether it passes the emergency gate.
3. Shrink the change to the minimum fix.
4. Confirm the change directly addresses the emergency.
5. Review for correctness, blast radius, rollback, and obvious safety issues first.
6. Run the fastest meaningful verification available.
7. Record skipped normal checks and why they were skipped.
8. Merge or release only if the emergency risk is greater than the code risk.
9. After the emergency is resolved, perform a normal-depth follow-up review.
10. File cleanup, tests, documentation, and postmortem tasks immediately so they are not lost.

## Emergency Review Checklist

- Scope: Is this the smallest change that resolves the urgent condition?
- Correctness: Does it actually fix the production, security, legal, or launch issue?
- Containment: Can it be rolled back or disabled quickly?
- Tests: What automated or manual check gives the most confidence right now?
- Observability: How will the team know whether the fix worked?
- Side effects: What users, data, jobs, APIs, or deployments can be harmed?
- Follow-up: What normal review items, tests, docs, or cleanup must happen after?

## Output Template

```markdown
## Emergency Decision
QUALIFIES | DOES_NOT_QUALIFY | NEEDS_MORE_INFO

## Reason
[Concrete reason tied to production user impact, security, legal/compliance, major launch, or hard external deadline.]

## Minimum Safe Change
- ...

## Immediate Verification
- ...

## Release / Rollback Notes
- ...

## Follow-up Required
- Normal-depth review:
- Tests:
- Cleanup:
- Documentation:
- Owner:
```

## Common Mistakes

- Treating urgency as an emergency.
- Expanding the hotfix to include nearby cleanup.
- Skipping all review instead of changing the review focus.
- Forgetting to perform a normal review after the incident is resolved.
- Letting emergency exceptions become the team's normal release process.

© agentara · MIT · agentara/skills

Similar skills

All skills for Code review and refactoring →

From the same set20

The whole set →
feature-dev-loop feature-dev-loop orchestrates multi-step feature development: planning, subagent reviews, TDD execution, and HTML acceptance reports. CX Codex +1 187installs publish-research-site The publish-research-site skill turns a topic or thesis into an interactive, image-rich site backed by citations, then deploys it with Vercel CLI. Use it to publish a research report or an interactive story. CX Codex +1 142installs torn-paper-collage-poster Generates image-generation prompts and workflows for editorial torn-paper collage posters with ripped edges, tape, and stamps. CX Codex +1 135installs engineering-small-prs engineering-small-prs turns a large feature, refactor or migration into small pull requests, with a merge order and a rollback plan. CX Codex +1 133installs engineering-code-review engineering-code-review applies Google engineering practices to review pull requests and local diffs. Focuses on overall code health, tests, and risk without nitpicking style. CX Codex +1 131installs engineering-review-comments engineering-review-comments turns rough review notes into PR comments with a severity label, an engineering reason and a concrete ask. CX Codex +1 125installs engineering-review-feedback engineering-review-feedback — a skill that teaches the agent to handle reviewer comments as the change author: apply fixes, draft replies, resolve disagreements. CX Codex +1 124installs engineering-change-descriptions engineering-change-descriptions is a Claude Code skill for drafting and rewriting PR descriptions, commit messages, and change summaries, including what changed, why, and how it was checked. CX Codex +1 124installs

Project sponsors

Companies that keep this analytics open