hotfix_skill

Overview

This skill fast-tracks fixes for urgent production incidents in a TypeScript FinOps stack. It codifies an expedited branch, test, PR, and alert workflow so teams restore service quickly with minimal risk. The goal is predictable, repeatable hotfixes that prioritize safety and speed.

How this skill works

The skill inspects the incident context and guides you through a five-phase flow: create a hotfix branch from main, implement the smallest possible fix, verify locally, open a labeled HOTFIX PR for expedited review, and send an urgent team alert. It enforces checks like typecheck and lint, forbids new features or refactors, and includes post-merge synchronization back to develop.

When to use it

• Production service is down or severely degraded
• A critical bug impacts customers or revenue
• A verified security vulnerability needs immediate patching
• When user-facing data integrity or billing flows are broken
• When an incident response requires prioritized, minimal-change remediation

Best practices

• Branch from main and keep changes minimal to reduce risk
• Run typecheck and lint before pushing to catch obvious errors
• Avoid adding features or refactoring during the hotfix
• Create a clear HOTFIX PR title and label to trigger expedited review
• Send a concise urgent alert with impact, fix summary, PR link, and requested reviewers
• Merge main back into develop and document an incident report if the issue was major

Example use cases

• Critical invoice extraction bug causing incorrect billing calculations in production
• Receipt ingestion pipeline outage that blocks revenue reporting
• High-severity regression introduced in deploy that breaks user checkout
• Security patch for exposed credentials or privilege escalation vector
• Emergency fix for a data routing rule that misclassifies financial transactions