hotfix-triage
Urgent issue classification, root cause analysis, and fast-path routing for production hotfixes
Best use case
hotfix-triage is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Urgent issue classification, root cause analysis, and fast-path routing for production hotfixes
Teams using hotfix-triage should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/hotfix-triage/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How hotfix-triage Compares
| Feature / Agent | hotfix-triage | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Urgent issue classification, root cause analysis, and fast-path routing for production hotfixes
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Hotfix Triage ## Capabilities Rapidly classifies production issues by severity, locates root causes from logs and stack traces, and routes to the appropriate fix path. Simple fixes skip planning entirely for maximum speed. ## Tool Use Instructions - Use **Read** to examine log files and error reports - Use **Grep** to search for error patterns and stack trace references in code - Use **Glob** to find affected source files - Use **Bash** to reproduce issues and check system state - Use **Write** to generate triage reports ## Process Integration - Used in `maestro-hotfix.js` (Triage and Root Cause) - Agent: Hotfix Specialist - Severity levels: critical (immediate), high (same-day), medium (next-sprint) - Simple fixes skip planning phase - High-risk fixes require human approval breakpoint
Related Skills
process-builder
Scaffold new babysitter process definitions following SDK patterns, proper structure, and best practices. Guides the 3-phase workflow from research to implementation.
babysitter
Orchestrate via @babysitter. Use this skill when asked to babysit a run, orchestrate a process or whenever it is called explicitly. (babysit, babysitter, orchestrate, orchestrate a run, workflow, etc.)
yolo
Run Babysitter autonomously with minimal manual interruption.
user-install
Install the user-level Babysitter Codex setup.
team-install
Install the team-pinned Babysitter Codex workspace setup.
retrospect
Summarize or retrospect on a completed Babysitter run.
resume
Resume an existing Babysitter run from Codex.
project-install
Install the Babysitter Codex workspace integration into the current project.
plan
Plan a Babysitter workflow without executing the run.
observe
Observe, inspect, or monitor a Babysitter run.
model
Inspect or change Babysitter model-routing policy by phase.
issue
Run an issue-centric Babysitter workflow.