ship

Commit, push, and open a GitHub pull request for a git branch.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ArthTech-AI/Marketplace-extensions --skill ship-arthtech-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/ArthTech-AI/Marketplace-extensions/tree/main/skills/ship
Command: npx skills add https://github.com/ArthTech-AI/Marketplace-extensions --skill ship-arthtech-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the friction of turning finished changes into a shared pull request by handling the commit, push, and PR creation steps in one guided workflow.

Core Features & Use Cases

  • Pre-flight safety checks: Verifies the working tree and prevents accidental pushes from the main branch.
  • Commit automation: Stages relevant changes and creates a concise commit message when the user does not provide one.
  • GitHub PR publishing: Pushes the branch, detects whether a pull request already exists, and creates a new one when needed.
  • Use case: A developer finishes a feature and wants to move from local edits to an open review-ready pull request without manually switching between git and GitHub commands.

Quick Start

Ask the assistant to run the ship workflow for the current branch, using your message if you have one or generating a commit message from the diff, then push the branch and open a GitHub pull request.

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 command?

To commit, push, and create a pull request in one command, you can run a guided workflow that stages changes, publishes the branch to GitHub, and opens a review-ready PR with a summary and test plan. This eliminates manual terminal hopping.

Can I automatically generate a git commit message from my diff?

Yes, you can automatically generate a git commit message from your diff. When you do not provide a custom message, the workflow analyzes your staged changes and creates a concise commit message automatically before pushing to GitHub.

Does this workflow prevent accidental pushes from the main branch?

Yes, this workflow prevents accidental pushes from the main branch. It enforces branch safety by running pre-flight checks that verify the working tree and ensure you are operating on a feature branch before publishing to GitHub.

What happens if a GitHub pull request already exists for my branch?

If a GitHub pull request already exists for your branch, the workflow detects it during the publishing step. It ensures you do not create duplicate pull requests and safely pushes any new upstream commits to the existing PR.

How do I handle upstream push recovery when publishing a git branch?

To handle upstream push recovery when publishing a git branch, the workflow automatically manages the push process and recovers from upstream conflicts. It safely pushes your changes to GitHub without failing the PR creation step.

Is there a way to standardize pull request output with a summary and test plan?

Yes, you can standardize pull request output with a summary and test plan. The workflow creates standardized PR output automatically, packaging your feature branch delivery for review without requiring manual formatting.