ship

Squash commits, push a feature branch, and open a pull request via GitHub CLI.

1|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/josorio7122/pi-flow --skill ship-josorio7122
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/josorio7122/pi-flow/tree/main/skills/ship
Command: npx skills add https://github.com/josorio7122/pi-flow --skill ship-josorio7122

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of preparing a completed feature branch for merging into the main codebase, ensuring a clean and professional commit history and a well-documented pull request.

Core Features & Use Cases

  • Commit History Management: Reviews and squashes commits for clarity and conciseness.
  • Automated Pushing: Pushes the finalized branch to the remote repository.
  • Pull Request Creation: Opens a new pull request with a structured title and body.
  • Worktree Cleanup: Removes the temporary worktree associated with the feature branch.
  • Use Case: After successfully implementing and testing a new feature, use this Skill to automatically clean up your commits, push the branch, and open a PR, ready for code review.

Quick Start

Use the ship skill to finalize the current feature branch and open a pull request.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I squash commits and open a pull request from a feature branch?

Squashing commits and opening a pull request is handled by reviewing your commit history, condensing it for clarity, pushing the finalized branch to origin, and creating the PR using the GitHub CLI.

What is the best way to clean up a git worktree after completing a feature?

Cleaning up a git worktree after feature completion involves removing the temporary worktree as part of the branch finalization process, ensuring your local workspace stays organized.

Can I automatically create a GitHub pull request from the command line?

Yes, you can automatically create a GitHub pull request from the command line by using the GitHub CLI within an automated workflow that pushes your branch and opens the PR with a structured title and body.

How do I standardize commit history before merging a feature branch?

Standardizing commit history before merging involves squashing commits into a concise sequence, which ensures a professional and readable project timeline for code reviewers.

Do I need the GitHub CLI to automate branch management and pull request creation?

Yes, you need the GitHub CLI to automate branch management and pull request creation, as the workflow relies on it to push finalized branches and open PRs with structured documentation.