mcpbeat

Incident Hotfix

hoangnguyen0403/incident-hotfix

Mitigate a production incident or urgent regression first, then route to root-cause remediation and a postmortem.

754 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
536
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/HoangNguyen0403/agent-skills-standard --skill incident-hotfix

The instruction itself

8 sections, as written by the author

Incident Hotfix Skill

> [!IMPORTANT]

> Mitigate a production incident or urgent regression first, then route to root-cause remediation and a postmortem.

Optional args: slug=<feature>, ticket=<id/url>, mode=interactive|autonomous|channel, channel=<id>, auto_continue=true|false, profile=business|hybrid|technical.

Instructions

When the user asks to perform this workflow, execute the following steps:

Incident Hotfix Workflow

Goal: Stop user-facing harm immediately, then hand off to root-cause discipline instead of debugging live.

Steps

  • Triage:
  • Severity, blast radius, affected environments/markets, and whether the regression is a rollback candidate.
  • Load deploy-release rollback path and prior deployment report if present.
  • Mitigate first:
  • Prefer rollback, feature flag disable, or config revert over a live code fix.
  • Confirm mitigation stopped user-facing harm before investigating root cause.
  • Do not attempt a root-cause code fix under live production pressure.
  • Stabilize:
  • Monitor logs, metrics, errors, and core user flows until signals return to baseline.
  • Record mitigation timestamp, owner, and evidence.
  • Route to remediation:
  • Once stable, hand off to dev-fix for root-cause debugging under the normal Propose -> Approve -> Verify cycle.
  • Do not skip dev-fix's root-cause-before-code requirement just because mitigation already shipped.
  • Route to learning:
  • After verify-work confirms the permanent fix, route to retro-learn for a postmortem.

Runtime Contract

  • Use only for production incidents or urgent regressions with active user-facing harm; non-urgent bugs go directly to dev-fix.
  • Required inputs: incident signal (alert, report, or error spike) plus a mitigation path (rollback, flag, or config revert).
  • Return BLOCKED only when no mitigation path exists and the incident cannot be safely stopped.

Handoff Payload

  • slug, operator_profile (carried, not re-inferred), severity, mitigation applied, stabilization evidence, outcome report, next workflow.

Blocking Questions

  • Ask max 3 at a time with a recommended default and 2-3 options.

Output Template

# Incident Hotfix: [Name]

## Severity And Blast Radius

## Mitigation Applied

## Stabilization Evidence

| Signal | Before | After |
| --- | --- | --- |
| [signal] | [value] | [value] |

## Root Cause Handoff

## Outcome Report
feature_status: partially_implemented | blocked
requirement_trace: BRD-OBJ-* -> REQ-* -> AC-* -> SRS-* -> evidence
completed_evidence: []; missing_evidence: []; decision_needed: []; recommended_next_workflow: dev-fix

## Next Workflow
dev-fix | verify-work | retro-learn

## Cost Report
Call `get_session_cost(workflow="incident-hotfix")` before final handoff.

How to use it

Copy the folder

Take hoangnguyen0403/incident-hotfix from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.