Create and manage emergency hotfix branches with audit trails and approvals.
npx skills add https://github.com/emcconnell/nova-scout --skill hotfix-emcconnell
Please help me install this Agent Skill. Skill: hotfix Source: https://github.com/emcconnell/nova-scout/tree/main/.claude/skills/hotfix Command: npx skills add https://github.com/emcconnell/nova-scout --skill hotfix-emcconnell
This Skill provides a controlled emergency workflow to bypass normal sprint processes and deliver minimal, auditable hotfixes for critical in-production bugs, ensuring fixes are tracked, approved, tested, and backported safely.
Use the /hotfix command with a bug ID or short description to initiate the emergency hotfix workflow and create the hotfix record.
High-intent search queries and answers about installing and using this skill.
An emergency hotfix workflow bypasses normal sprint processes to deliver minimal, auditable fixes for critical in-production bugs. You need it when urgent bugs require rapid branch creation, tracked approvals, QA gating, and safe backporting to release and development branches.
To create a hotfix branch with an audit trail, initiate the workflow using a bug ID or description. The system drafts a markdown record capturing problem, root cause, fix details, testing, approvals, and rollback plan, while enforcing minimal-scoped changes from a release tag or main branch.
Yes, the hotfix workflow orchestrates parallel approvals from lead-programmer, qa-tester, and producer roles. It enforces QA re-entry gates—ranging from smoke checks to full QA—and ensures all critical approvals are tracked before deployment proceeds.
To backport a hotfix safely, the workflow guides backport merges to both release and development branches after applying minimal-scoped fixes. It enforces QA gating and generates a documented rollback plan to ensure safe integration across all branch environments.
Post-deploy verification includes producing a deployment summary, updating bug status, and performing verification steps. The hotfix workflow also schedules a post-incident review within 48 hours to ensure the critical bug fix is fully documented and resolved.
Bypassing sprint processes for emergency bug fixes requires strict enforcement of minimal-scoped changes to prevent scope creep. Limitations include the necessity of coordinated parallel approvals and mandatory QA gating, which can delay deployment if stakeholders are unavailable.
akiojinCreate a hotfix branch, guide fixes, open a pull request to main, and confirm patch releases.
niclasmartinsson-sysAutomate Google Docs post-mortem creation, calendar review scheduling, and Chat notifications.
SeongHuniOrchestrate QA leads and testers through test plan generation, test case writing, smoke checks, manual execution, and sign-off reports.
shotleybuilderAutomate emergency hotfix branches for the ash_cookie_consent library.
