ship

Push GitHub branches and create pull requests with derived titles and bodies.

2|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/wilsonfaustino/ai-tools --skill ship-wilsonfaustino
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/wilsonfaustino/ai-tools/tree/main/skills/ship
Command: npx skills add https://github.com/wilsonfaustino/ai-tools --skill ship-wilsonfaustino

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually pushing branches and writing pull request descriptions is time-consuming, often inconsistent, and fails to capture the intent behind code changes, leading to unclear review context for collaborators.

Core Features & Use Cases

  • Pre-flight Safety Checks: Validates GitHub authentication, branch state, and commit history before any push to avoid broken or accidental changes.
  • Intent-Driven PR Generation: Automatically creates PR titles and bodies from branch names and commit history, focusing on the purpose of changes rather than just listing modified files.
  • Stacked PR Support: Detects PR stacks and optionally includes a stack section in the PR body for linked, dependent changes.
  • Label Management: Maps branch prefixes to repository labels and auto-creates missing labels if approved by the user.
  • Existing PR Updates: Handles updates to open PRs with options to overwrite, append, or skip body updates when new commits are pushed. Use case: For example, after finishing a feature branch for user migration, this skill automates the entire push and PR creation process, generating a clear description that explains the migration's business purpose instead of listing every modified file.

Quick Start

Use the ship skill to push my current feature branch and create a pull request with a clear description of the changes.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate GitHub pull request creation from a branch?

You can automate GitHub pull request creation by using a tool that pushes branches and generates intent-driven PR titles and bodies directly from branch naming conventions and commit history. This eliminates manual, inconsistent PR workflows and clarifies review context.

What is the best way to generate a PR description from commit history?

Generating a PR description from commit history is best handled by intent-driven PR automation, which derives the title and body from commits and branch names. This focuses on the purpose of changes rather than just listing modified files.

How do I manage stacked PRs on GitHub?

Managing stacked PRs on GitHub is supported by automation that detects PR stacks and optionally includes a stack section in the PR body for linked, dependent changes. This ensures dependent branches are properly tracked during code review.

Can I automatically map branch prefixes to GitHub labels?

Yes, you can map branch prefixes to repository labels automatically. The automation validates existing labels and can auto-create missing labels if approved by the user, ensuring consistent categorization across pull requests.

Does GitHub PR automation support updating existing open PRs?

GitHub PR automation supports updating existing open PRs when new commits are pushed. It provides options to overwrite, append, or skip body updates, ensuring PR descriptions remain accurate without losing existing review context.

What pre-flight safety checks are needed before pushing a git branch?

Pre-flight safety checks needed before pushing a git branch include validating GitHub authentication, branch state, and commit history. These validations prevent broken or accidental changes from being pushed to the remote repository.