Incident Hotfix Agent Skill
Mitigate a production incident or urgent regression first, then route to root-cause remediation and a postmortem.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/HoangNguyen0403/agent-skills-standard --skill incident-hotfixThe instruction itself
8 sections, as written by the authorIncident 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-releaserollback 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-fixfor 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-workconfirms the permanent fix, route toretro-learnfor 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.
Other skills for the same job
different authors, same section of the catalogue
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Use when implementing any feature or bugfix, before writing implementation code
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
Expert guidance for systematic backtesting of trading strategies. Use when developing, testing, stress-testing, or validating quantitative trading strategies. Covers "beating ideas to death" methodology, parameter robustness testing, slippage modeling, bias prevention, and interpreting backtest results. Applicable when user asks about backtesting, strategy validation, robustness testing, avoiding overfitting, or systematic trading development.
Cloud laboratory platform for automated protein testing and validation. Use when designing proteins and needing experimental validation including binding assays, expression testing, thermostability measurements, enzyme activity assays, or protein sequence optimization. Also use for submitting experiments via API, tracking experiment status, downloading results, optimizing protein sequences for better expression using computational tools (NetSolP, SoluProt, SolubleMPNN, ESM), or managing protein design workflows with wet-lab validation.
This skill should be used for time series machine learning tasks including classification, regression, clustering, forecasting, anomaly detection, segmentation, and similarity search. Use when working with temporal data, sequential patterns, or time-indexed observations requiring specialized algorithms beyond standard ML approaches. Particularly suited for univariate and multivariate time series analysis with scikit-learn compatible APIs.
How to use it
Take hoangnguyen0403/incident-hotfix from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
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.