push

Push the current Git branch to origin with branch safety checks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Pushing code to a remote repository carries risks like accidentally pushing directly to a protected main branch, force-pushing over shared history, or pushing uncommitted work. This Skill enforces branch safety rules so pushes happen only under the right conditions. ## Core Features & Use Cases - Branch Protection: Refuses to push main or master directly in PR-gated repositories and directs the user to open a pull request from the homolog branch instead. - Direct-Main Detection: Reads the police.direct_main flag from .bravros/config.json via the bravros CLI to distinguish direct-main personal repos from PR-gated team repos. - Safety Gates: Blocks force pushes unless explicitly requested and stops when the working tree is dirty, pointing to /ship or /commit first. - Use Case: After committing a hotfix on the homolog branch, ask the agent to push; it verifies the branch policy and pushes only the current branch to origin without committing or creating a PR. ## Quick Start Ask the agent to push my current branch to origin and it will run the branch safety checks before pushing.

Frequently Asked Questions about push

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

FAQPage Schema
How do I push my current Git branch to origin safely?▼

Invoke the push skill after committing your work. It pushes only the current branch to origin, verifies branch protection rules first, and never commits or creates pull requests on its own.

Why does pushing to main get refused?▼

Direct pushes to main or master are refused in PR-gated repositories, where changes must flow through a pull request from the homolog branch. The check reads police.direct_main from .bravros/config.json; only a value of true allows pushing main.

Can I push main directly in a personal repository?▼

Yes, if the repository declares police.direct_main: true in .bravros/config.json, set via bravros police direct-main on or scaffolded by /git-this. In that mode there is no staging branch and pushing main is the normal flow.

Does the push skill allow force pushing?▼

Force pushes are blocked by default. They proceed only when the operator explicitly requests one, protecting shared remote history from accidental overwrites.

What happens if my working tree is dirty when I push?▼

The push stops and directs you to /ship or /commit first. Committing changes is the responsibility of those skills, not the push skill, so uncommitted work is never silently included.