bp-push

Push the current Git branch to the remote with branch guardrails.

4|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/skaisser/blueprint --skill bp-push
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bp-push
Source: https://github.com/skaisser/blueprint/tree/main/skills/bp-push
Command: npx skills add https://github.com/skaisser/blueprint --skill bp-push

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures safe, auditable pushes by preventing accidental pushes to protected branches and requiring a clean working tree, thereby reducing risky commits to shared remotes.

Core Features & Use Cases

  • Guarded pushes: Blocks pushes to main/master and prompts for staging or feature branches.
  • Pre-flight validation: Checks branch status, uncommitted changes, and branch naming to enforce workflow rules.
  • Operational use case: A developer attempts to push on a feature branch; the skill validates the environment and pushes only after meeting criteria.

Quick Start

Run the /bp-push command to push your current branch to the remote while enforcing branch safeguards.

Frequently Asked Questions about bp-push

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

FAQPage Schema
How do I prevent accidental git pushes to protected branches like main or master?

To prevent accidental pushes to protected branches, this Skill enforces pre-flight validation checks that block pushes to main or master, prompting you to use staging or feature branches instead. It ensures a clean working tree before pushing to the remote repository.

What pre-flight checks are needed before pushing a git branch to remote?

Pre-flight checks needed before pushing a git branch include verifying branch status, checking for uncommitted changes, and enforcing branch naming conventions. These guardrails ensure a clean working tree and prevent unsafe commits to shared remotes.

Does this guarded git push workflow support teams with staging and feature branches?

Yes, this guarded git push workflow explicitly supports teams adopting Git workflows with protected main/master and staging branches. It validates the environment and enforces branch guard rules to ensure pushes only occur when criteria are met.

Why does my git push fail with branch protection rules and uncommitted changes?

Your git push fails because branch protection rules require a clean working tree and valid branch naming. The Skill provides clear error messaging when uncommitted changes or branch guard rules block the push, preventing risky commits to shared remotes.

What is the best way to enforce DevOps safety checks during a git push?

The best way to enforce DevOps safety checks during a git push is to use guardrails that validate branch status and block protected branches automatically. This Skill audits the environment and provides clear error messaging to prevent unsafe remote updates.