ship

Automate Git commits, pushes, and GitHub pull request creation.

1|Updated Jan 12, 2026

Search Tags:#automation #git #devops #code review #pull request #github

Ready to run

npx skills add https://github.com/cwilliams5/Alt-Tabby --skill ship-cwilliams5

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/cwilliams5/Alt-Tabby/tree/main/.claude/skills/ship
Command: npx skills add https://github.com/cwilliams5/Alt-Tabby --skill ship-cwilliams5

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh.

What problem does it solve?

This Skill streamlines the process of getting your code changes from your local machine into a pull request, ready for review.

Core Features & Use Cases

Automated Git Workflow: Handles staging, committing, pushing, and PR creation in one go.
Standardized Commits: Ensures commit messages and PR bodies follow a consistent, documented format.
Use Case: After completing a feature or bug fix, you can use this Skill to quickly and reliably prepare your changes for merging into the main codebase.

Quick Start

Use the ship skill to commit, push, and create a pull request for your current work.

Frequently Asked Questions about ship

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

FAQPage Schema

How do I automate committing, pushing, and creating a GitHub pull request at the same time?▼

To automate committing, pushing, and creating a pull request, you can use a workflow tool that stages all changes, pushes to origin with upstream tracking, and generates a GitHub PR with a title and test plan in one go.

Do I need the gh CLI to automate my Git workflow and create pull requests?▼

Yes, you need the gh CLI installed to automate creating pull requests. The workflow relies on it to generate the PR with a detailed summary, test plan, and issue closing references on GitHub.

How do conventional commit standards affect automated pull request creation?▼

Automated pull request creation enforces conventional commit standards to ensure commit messages and PR bodies follow a consistent, documented format, which helps maintain clarity for code reviews and project history.

What is the best way to format a pull request body for a code review?▼

The best way to format a pull request body is to include a short title, detailed summary, test plan, and issue closing references. This standardized format ensures reviewers have all necessary context.

Can I stage all local changes and push to origin with upstream tracking automatically?▼

Yes, you can stage all local changes and push to origin automatically. The automation handles staging all modifications and pushing them while setting up upstream tracking for your current branch.