hotfix

To deploy an urgent fix to the main branch while bypassing QA, this Skill confirms P0 status, cuts a git worktree, cherry-picks commits, and merges back into the integration branch for rapid production deployment.

The git workflow for cherry-picking urgent fixes involves cutting a worktree from the main branch, applying the necessary commits, and merging them back into the integration branch to resolve critical production issues quickly.

Yes, you need to use git worktrees for branch management during a hotfix because the Skill utilizes them to isolate the urgent fix environment before cherry-picking commits into the main integration branch.

Yes, you can automate the branching process for P0 production issues as this Skill automatically generates and manages branches for hotfixes, requiring only the /hotfix --confirm command to initiate the workflow.

The best way to handle a critical production fix without disrupting the CI/CD pipeline is confirming the P0 status, cutting a dedicated worktree, and cherry-picking the urgent fix directly to the integration branch.

You should not use a hotfix workflow for urgent fixes if the issue lacks confirmed P0 status, as this process specifically bypasses standard QA stages to speed up production deployments for critical issues only.