Production Hotfix

Ships a small fix directly to main without going through the release PR pipeline, then backmerges main into dev so the two branches stay in sync. Normal changes still go through /release — this exists only for urgent fixes that cannot wait.

When NOT to use this

• Multi-file refactors or feature work → use /release
• Anything that needs CodeRabbit review or a second pair of eyes → use /release
• Changes touching migrations, auth, billing, or anything with a non-trivial blast radius → too risky for the bypass, open a hotfix PR instead

Prerequisites

• The fix is scoped to one or two files, minimal blast radius
• You have admin permissions on the repo (the push to main bypasses branch protection — non-admins get rejected outright)
• No concurrent release PR is in flight (check with gh pr list --label release)

Starting states this skill handles

The workflow branches on what state the local checkout is in when the skill runs: