bp-ship

Commit and push feature branch changes with a main-branch safety gate.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Commit and push changes in one go with a branch safety gate to prevent accidental pushes to main and to streamline the feature-branch workflow.

Core Features & Use Cases

  • Branch Safety Check: prevents pushing directly to main/master and enforces a PR-like workflow for feature work.
  • Single-step commit + push: combines /bp-commit and /bp-push into a seamless action.
  • Guardrails: avoids staging secrets or env files and requires staying on a feature branch until ready to ship.

Quick Start

Use bp-ship to commit and push your changes on the current branch with safety checks.

Frequently Asked Questions about bp-ship

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

FAQPage Schema
How do I automate git commit and push in one step while preventing direct pushes to main?

This single-step commit and push automation enforces a branch safety gate that rejects direct pushes to main or master, ensuring feature branch workflows are enforced before any code is shipped.

How does branch safety check work when automating git workflow commits?

Branch safety check works by verifying the current git branch before pushing, rejecting any commit and push workflow attempts that target main or master to enforce a PR-like feature branch process.

Can I use an automated commit and push workflow without creating a pull request?

Yes, you can use an automated commit and push workflow without creating a pull request, as the process explicitly focuses on sequencing commit and push actions while skipping PR creation entirely.

Does automated git commit and push staging block secrets and environment files?

Automated git commit and push staging blocks secrets and environment files by enforcing guardrails that prevent sensitive files from being staged, ensuring only safe code changes are committed and pushed.

What are the limitations of using a single-step commit and push automation for feature branches?

Limitations include the inability to create pull requests, strict rejection of direct pushes to main or master, and the requirement to remain on a feature branch until ready to ship changes.