ship

Commit changes, push with upstream, and create a pull request.

Updated Feb 23, 2026
One-click install
npx skills add https://github.com/duanegoodner/agentrelay --skill ship-duanegoodner
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/duanegoodner/agentrelay/tree/main/.claude/skills/ship
Command: npx skills add https://github.com/duanegoodner/agentrelay --skill ship-duanegoodner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Commit, push, and open a PR for the current feature branch, automating the git workflow and reducing manual steps.

Core Features & Use Cases

  • End-to-end git flow automation: Stage changes, commit with a concise message, push (-u), and open a pull request.
  • PR metadata & consistency: Generates a PR with a consistent body shape to facilitate code reviews and collaboration.
  • Use Case Example: A feature branch on a developer's repo is automatically prepared for review by creating a PR after the commit and push steps.

Quick Start

Run the ship skill to automatically commit changes, push the branch, and open a PR.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I commit, push, and create a pull request in one step?▼

To commit, push, and create a pull request in one step, you can use an automation tool that stages changes, commits with a message, pushes with upstream, and invokes gh pr create. This automates the feature-branch workflow to prepare code for review.

What is the best way to automate GitHub pull request creation from a local branch?▼

The best way to automate GitHub pull request creation is using a CLI workflow that pushes the local branch with -u and runs gh pr create with a structured body. This ensures consistent PR metadata for collaborative code reviews.

Does git flow automation work in CI pipelines and local development?▼

Yes, git flow automation works in CI pipelines and local development. It is designed for typical feature-branch development in GitHub-based workflows, using standard CLI tools to stage, commit, push, and open pull requests across collaborative teams.

How does automated branch management handle commit messages and PR bodies?▼

Automated branch management handles commit messages and PR bodies by writing concise commit messages and generating a pull request with a consistent body shape. This enforces safe handling of sensitive data and facilitates code reviews.

Do I need the GitHub CLI to automate opening a pull request?▼

Yes, you need the GitHub CLI (gh) to automate opening a pull request. The workflow invokes gh pr create with a structured body and summary after staging changes with git add and pushing the feature branch with upstream.