hotfix

Route urgent production bug fixes through tech-lead, dev, QA, and reviewer gates.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/cuongnm-dev/team-ai-config --skill hotfix-cuongnm-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hotfix
Source: https://github.com/cuongnm-dev/team-ai-config/tree/main/cursor/skills/hotfix
Command: npx skills add https://github.com/cuongnm-dev/team-ai-config --skill hotfix-cuongnm-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines urgent, well-defined production bug fixes by bypassing BA/SA analysis and routing directly from tech-lead to dev to QA to reviewer for rapid deployment.

Core Features & Use Cases

  • End-to-end hotfix workflow for production bugs with clearly identified root cause and scoped changes.
  • Role-based escalation and gates including root-cause verification, QA, and reviewer sign-off.
  • Artifact generation and traceability through hotfix-id creation, state tracking, and integration with feature-map updates.

Quick Start

Trigger the hotfix workflow by specifying the root cause and the scope, and let the dispatcher route the fix through QA and reviewer gates.

Frequently Asked Questions about hotfix

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy an urgent production bug fix without full BA and SA analysis?

Urgent production bug fixes can bypass BA/SA analysis by routing directly from tech-lead to developer through QA and reviewer gates. This hotfix pipeline enforces root-cause identification and limits scope to a small set of files for rapid deployment.

What is the hotfix workflow for escalating scoped production incidents?

The hotfix workflow is a dispatcher-driven escalation process for production incidents. It routes well-defined bugs from tech-lead to developer to QA to reviewer, enforcing root-cause verification, QA review, and reviewer sign-off before deployment.

Can I use this hotfix pipeline for both mono-repos and mini-repos?

Yes, the hotfix pipeline applies to both mini-repos and mono-repos. It enforces root-cause identification and restricts scope to a small set of files across either repository structure for rapid production deployment.

How do I track state and documentation after a hotfix deployment?

Track state and documentation after a hotfix deployment using post-merge governance. This process generates traceability through hotfix-id creation, state tracking, and integration with feature-map updates.

What do I need to start an urgent hotfix deployment?

To start an urgent hotfix deployment, specify the root cause and the scope of the production bug. The dispatcher then routes the fix through QA and reviewer gates for rapid production deployment.

When should I not use a direct hotfix pipeline for incident response?

Do not use the direct hotfix pipeline when a production bug lacks a clearly identified root cause or scoped changes. The pipeline requires root-cause verification and limits changes to a small set of files.