branch-ship

Create feature branches, commit with conventional messages, and push to remote repositories.

Updated Apr 22, 2025
One-click install
npx skills add https://github.com/mcampbellr/.dotfiles --skill branch-ship
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: branch-ship
Source: https://github.com/mcampbellr/.dotfiles/tree/main/claude/.claude/skills/branch-ship
Command: npx skills add https://github.com/mcampbellr/.dotfiles --skill branch-ship

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill simplifies the process of creating a feature branch, committing changes, and pushing them to a remote repository, ensuring a safe and standardized workflow.

Core Features & Use Cases

  • Branch Creation: Automatically creates a feature branch from a base branch.
  • Commit Automation: Commits changes with a conventional message format.
  • Pushing with Safety: Pushes changes to the remote repository without force pushes or amending commits.
  • Use Case: Ideal for developers who want to quickly and safely create a new feature branch, stage their changes, and prepare them for deployment.

Quick Start

Use the /branch-ship command to create a new feature branch and push your changes. Optionally, provide a branch name to customize the branch name. For example: /branch-ship my-feature-branch

Frequently Asked Questions about branch-ship

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

FAQPage Schema
How do I automate creating a git feature branch and pushing it safely?

You can automate creating a git feature branch and pushing it safely by using a command that handles branch creation, commits changes with a conventional message, and pushes to the remote repository without force pushing.

What is the safest way to commit and push a new git feature branch?

The safest way to commit and push a new git feature branch is to use a standardized workflow that avoids force pushes and amending commits, ensuring remote repository integrity while applying conventional commit messages.

Can I customize the feature branch name when automating git commits?

Yes, you can customize the feature branch name when automating git commits by providing your desired branch name as an argument to the branch creation and deployment command.

How does conventional commit automation work for feature branches?

Conventional commit automation for feature branches works by staging your current changes and automatically generating a standardized commit message before safely pushing the branch to the remote repository.

Do I need any external git dependencies to automate safe feature branch pushes?

No external git dependencies are required to automate safe feature branch pushes, as the automation runs standalone using standard git commands for branch creation, committing, and remote pushing.

Are there limitations to automating git branch creation and deployment?

A limitation of automating git branch creation and deployment is that it strictly avoids force pushes and commit amending, meaning it may not be suitable for workflows requiring history rewriting or complex conflict resolution.