skills.rest
ippontech
ippontechOFFICIAL
Explore all skills by this author →
WebsiteGitHub

ship

Create or update a GitHub PR from local changes with conventional commits.

14|4|Updated Apr 8, 2026
Search Tags:#automation#git#workflow#branch#pull-request#conventional-commit
One-click install
npx skills add https://github.com/ippontech/terraform-provider-anthropic --skill ship-ippontech
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/ippontech/terraform-provider-anthropic/tree/main/.claude/skills/ship
Command: npx skills add https://github.com/ippontech/terraform-provider-anthropic --skill ship-ippontech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reduces manual toil by turning local work into a PR-ready branch, including branch creation, conventional-commit messages, pushing, and PR generation or updates.

Core Features & Use Cases

  • Branch generation and naming aligned with conventional formats
  • Commit messages that follow conventional commits for clear history
  • Push to origin and create or update a GitHub PR with a PR title/body derived from commits
  • Ideal for feature work, hotfixes, and collaborative development requiring traceable PRs

Quick Start

Turn my current work into a PR-ready branch by creating a branch, committing changes with a conventional message, pushing to origin, and opening a PR.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I automate creating a branch, committing changes, and opening a GitHub pull request?▼

To automate creating a branch, committing changes, and opening a GitHub pull request, this Skill wraps local work into a PR-ready branch by deriving a branch name, committing with a conventional message, pushing to origin, and opening or updating a PR.

How does conventional commit formatting work for automated pull requests?▼

Conventional commit formatting for automated pull requests works by enforcing deterministic commit messages that follow conventional formats, which are then used to automatically derive the PR title and body for clear history.

Can I update an existing GitHub PR instead of creating a new one?▼

Yes, you can update an existing GitHub PR instead of creating a new one. The workflow pushes new local commits to the origin branch and automatically updates the existing PR with the commit-derived description.

What is the best way to turn local feature work into a PR-ready branch?▼

The best way to turn local feature work into a PR-ready branch is using an automated workflow that handles branch generation, conventional commit messages, pushing to origin, and PR generation for traceable collaborative development.

Does this automated PR workflow handle branch naming for hotfixes and feature work?▼

Yes, this automated PR workflow handles branch naming for hotfixes and feature work by deriving branch names aligned with conventional formats, ensuring traceable PRs for both collaborative development contexts.

Related Skills

Explore More Software Engineering Skills→
alexandersumeralexandersumer
1

git-publish-to-origin

Commit and push the current Git branch to the origin repository with safety checks.

Community
Intermediate
julianobarbosajulianobarbosa
7

Git

Automate Git commit, branch, merge, and PR workflows with GitHub CLI and security checks.

Community
Advanced
k97k97
4

finishing-a-development-branch

Verify tests before merging or cleaning up git development branches.

Community
Intermediate
sqfzysqfzy

git

Generate conventional commit messages and update changelogs from repository state.

Community
Advanced