promote

Merges accumulated homolog branch work into main via a gated pull request workflow.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Promoting staging work to production often involves manual merge steps that are error-prone and unaudited. This Skill enforces a controlled homolog → main merge with human-presence verification, merge locking, and automatic plan closure so production releases stay deliberate and traceable. ## Core Features & Use Cases - Human-presence gating: Requires a short-lived token minted out-of-band via bravros promote unlock in a separate terminal, so the agent cannot authorize its own production merge. - Guarded PR merge flow: Snapshots the pre-merge main tip as a git ref, opens a PR with an accurate commit range, waits for clean mergeability, acquires a merge lock, and merges with the literal PR number. - Post-merge close-out: Fast-forwards homolog from main, closes only the plans actually shipped in the promoted range, revokes the single-use token, and sends a PT-BR announcement. - Use Case: After a week of feature work has accumulated on the homolog branch and passed review, run /promote to ship it to production with a verified audit trail instead of a manual merge. ## Quick Start Ask the agent to run /promote to merge the current homolog branch into main after minting the unlock token in a separate terminal.

Frequently Asked Questions about promote

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

FAQPage Schema
How do I promote homolog branch work to main?▼

Run /promote with a clean homolog working tree that is up to date with its remote. The skill opens a PR from homolog to main, waits for clean mergeability, acquires a merge lock, merges, then syncs homolog back from main.

Why does the promote skill require a token from a separate terminal?▼

The token proves human presence at the keyboard before a production merge. It must be minted with `bravros promote unlock` in a non-agent terminal so the session requesting the merge cannot authorize its own merge.

What happens if the promote token expires before the merge?▼

The token is valid for 5 minutes and PR creation plus CI can consume it. The skill checks the TTL right before merging; if expired, it asks for exactly one re-mint and never loops the merge attempt.

Does the promote skill delete or prune branches after merging?▼

No, branch pruning is manual-only and /promote never prunes. The skill points the operator to the separate /prune-merged workflow for branch cleanup.

When should I use hotfix or finish instead of promote?▼

Use /hotfix for incident-driven production fixes and /finish for completing individual feature branches. The promote skill is only for calm-day merges of accumulated homolog work into main.