ship

Commit changes, push to the base branch, and create a conventional PR.

1|Updated Jan 18, 2026
One-click install
npx skills add https://github.com/knwoop/claude-code --skill ship-knwoop
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/knwoop/claude-code/tree/main/skills/ship
Command: npx skills add https://github.com/knwoop/claude-code --skill ship-knwoop

SYSTEM DOCUMENTATION & REQUIREMENTS

## What problem does it solve? Committing changes, pushing to the correct base branch, and creating a PR often requires adhering to host repository conventions; this skill standardizes the workflow to reduce drift and mistakes.

## Core Features & Use Cases

  • Infers the base branch (main or master fallback) and runs a set of diffs and logs to guide PR metadata.
  • Analyzes changed paths to infer a scope label when the repository uses scoped commit messages and PR titles, then formulates PR titles and descriptions accordingly.
  • Enforces repository-style conventions for PRs, ensuring consistency across teams and branches.

### Quick Start Use the ship skill to commit changes, push the current branch, and draft a PR that follows the host repository's conventions.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate git commit, push, and pull request creation in one workflow?

Automating the git workflow involves committing changes, pushing to the correct base branch, and creating a PR that adheres to host repository conventions. This reduces manual mistakes and standardizes collaboration outcomes.

How does an automated pull request tool infer the correct scope for PR titles?

An automated pull request tool analyzes changed file paths to infer a scope label when the repository uses scoped commit messages. It then formulates PR titles and descriptions according to the repository's specific style conventions.

How do I push code changes to the correct base branch without manually checking the default branch?

You can push code changes by using a tool that infers the base branch automatically, falling back from main to master if necessary. It runs diffs and logs to guide the metadata and ensure the push targets the correct branch.

Does automated git workflow tooling work with custom repository branching rules?

Yes, automated git workflow tooling works with custom repository branching rules by relying on standard git tooling and repository conventions. It enforces repository-style conventions to ensure consistency across teams and branches.

What is the best way to ensure PR descriptions match repository style conventions?

The best way to ensure PR descriptions match repository style conventions is to analyze changed paths and logs to infer scope, then format the PR titles and descriptions accordingly. This enforces consistency across the team.