hotfix

Ships urgent production fixes by committing, pushing to homolog, and merging a PR to main.

3|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/bravros/bravros --skill hotfix-bravros
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hotfix
Source: https://github.com/bravros/bravros/tree/main/plugins/core/skills/hotfix
Command: npx skills add https://github.com/bravros/bravros --skill hotfix-bravros

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? When production breaks, the normal plan-review-merge workflow is too slow. This Skill provides a controlled emergency path that commits an urgent fix, pushes it through the homolog staging branch, opens a PR to main, and merges it immediately — while still respecting the repository's hard safety gates. ## Core Features & Use Cases - Emergency merge pipeline: Confirms repo identity, commits only the changed files, pushes to homolog, creates a homolog→main PR, waits for mergeability, and merges with the literal PR number so the police hook can validate the command. - Safety gates preserved: Refuses to run on main/master, honors the autopr lock, never deletes the homolog branch, never skips the PR, and stops if targeted tests fail. - Post-merge hygiene: Syncs homolog back from main, closes the related plan via .planning/events.jsonl, reports an explicit deploy status line, and announces the fix in PT-BR. - Use Case: A payment bug is live in production. Run /hotfix fix null check in checkout totals and the agent commits the fix, merges it to main through the staging lane, and tells you whether a server rebuild and restart is still required. ## Quick Start Run /hotfix followed by a short description of the urgent production fix you want committed and merged to main.

Frequently Asked Questions about hotfix

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

FAQPage Schema
How do I deploy an emergency hotfix to production with GitHub?▼

Run /hotfix with a description of the fix. The skill commits only the changed files, pushes to the homolog branch, opens a homolog-to-main PR, waits for mergeability, and merges it immediately without the normal review workflow.

How does the hotfix skill bypass the normal PR review process?▼

Running /hotfix itself counts as approval for merge-to-main, so no review checkpoints occur between commit and merge. Hard gates still apply: the autopr lock, the police staging lane, and protected main requiring a PR.

Why does gh pr merge get blocked during a hotfix?▼

The police hook reads the raw command text, so the PR number must be a literal value like gh pr merge 1234 --merge, not a $VAR. It also requires head branch homolog, mergeStateStatus CLEAN, and no autonomous lock present.

Can I run a hotfix while an autopr lock is active?▼

No. If bravros autopr status reports a lock, the hotfix refuses to merge because an autonomous session holds the repo. Clear it with bravros autopr clear-lock from a separate terminal, then re-run /hotfix.

When should I not use the hotfix workflow?▼

Do not use it when the change can wait for normal review, when targeted tests fail, or when you are on main/master. If a review is wanted, it is not a hotfix and should go through the standard PR flow.