One-click install
npx skills add https://github.com/imclab/xrA1-swarm --skill hotfix-imclab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hotfix
Source: https://github.com/imclab/xrA1-swarm/tree/main/.claude/skills/hotfix
Command: npx skills add https://github.com/imclab/xrA1-swarm --skill hotfix-imclab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of shipping urgent bug fixes safely and traceably when normal sprint workflows are too slow.

Core Features & Use Cases

  • Emergency triage and gating: Categorizes severity (S1/S2) and stops immediately for lower-severity issues so you don’t misuse the hotfix process.
  • Controlled change management: Creates a structured hotfix record, proposes writing it to production hotfixes, and (when git is available) creates a dedicated hotfix branch.
  • Approval-driven deployment: Collects parallel sign-offs (lead-programmer, qa-tester, producer) and runs an explicit QA re-entry gate to decide between smoke check and targeted team QA before deploy.
  • Rollback and verification: Forces a rollback plan, updates the original bug status, deploys only after gates pass, and verifies with bug-report checks plus a post-incident review.

Quick Start

Request a hotfix by telling the team: "/hotfix [bug-id or description]" and follow the prompts to document the record, approvals, QA gate, and deployment steps.

Frequently Asked Questions about hotfix

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

FAQPage Schema
How do I manage an emergency hotfix workflow without losing audit traceability?▼

An emergency hotfix workflow manages critical defect resolution by creating a structured hotfix record, isolating changes in a dedicated git branch, and enforcing parallel approvals to ensure full audit traceability.

What is the process to ship an urgent bug fix safely when normal sprints are too slow?▼

Shipping an urgent bug fix safely requires severity-based triage to confirm S1/S2 eligibility, followed by creating a hotfix record, collecting sign-offs, and passing a QA re-entry gate before deployment.

How do I set up a rollback plan and QA gate before deploying a critical patch?▼

Setting up a rollback plan and QA gate forces explicit documentation of rollback procedures and requires a targeted team QA check or smoke test, ensuring the critical patch only deploys after passing these gates.

Can I use this incident triage process for minor defects that do not block production?▼

Incident triage for minor defects stops immediately because the hotfix workflow applies only to S1/S2 critical or major issues, preventing misuse of the emergency process for lower-severity problems.

What approvals do I need to collect before deploying a production hotfix?▼

Deploying a production hotfix requires collecting parallel sign-offs from a lead-programmer, qa-tester, and producer to ensure controlled change management and accountability across the team.

How does post-deploy verification work after an emergency code change?▼

Post-deploy verification runs bug-report checks to confirm the critical defect is resolved, updates the original bug status, and triggers a post-incident review to document the outcome.