Engineering Emergency Changes

What it does

When your agent uses it

• Rollback alternative
• Production/security/legal fix
• Hard external deadline claims expedited review
• Relaxed process

Example prompts

• “emergency change”
• “hotfix”
• “prod incident”
• “/engineering-emergency-changes”

Workflow steps

10 steps, taken from the first numbered list in SKILL.md.

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

What it can do on your machine

Read from SKILL.md and the folder at commit 950e1bf. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  Links to these hosts (documentation or services it may open):

  • google.github.io

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Engineering Emergency Changes loads about 985 tokens when it runs. Until then it costs about 131 tokens; SKILL.md has 438 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~131

When it runs · the whole SKILL.md, loaded when a task matches

~985

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from agentara/skills at commit 950e1bf, republished under its MIT licence (© agentara). 438 words, ~985 tokens.

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.

## 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:

© agentara, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/engineering/engineering-emergency-changes of agentara/skills.

Open the folder on GitHubat commit 950e1bf