skills.rest
danielsuguimoto
danielsuguimotoCOMMUNITY
Explore all skills by this author →
𝕏@djsuguimotoGitHub

ship-changes

Ships current work end-to-end by branching, committing, pushing, and opening a pull request.

Updated Jul 11, 2026
Search Tags:#git#code review#pull request#commit#shipping#push#branch
One-click install
npx skills add https://github.com/danielsuguimoto/skills --skill ship-changes-danielsuguimoto
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ship-changes
Source: https://github.com/danielsuguimoto/skills/tree/main/skills/ship-changes
Command: npx skills add https://github.com/danielsuguimoto/skills --skill ship-changes-danielsuguimoto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Shipping finished work involves a repetitive multi-step Git workflow — creating a categorized branch, writing a commit, pushing, and opening a PR — that is easy to do inconsistently or forget entirely. ## Core Features & Use Cases - Full shipping pipeline: Runs branch creation, commit, push, and PR creation as one orchestrated sequence with shared pre-scan context. - Change pre-scan: Scans uncommitted changes and ahead-of-upstream commits once, derives a change summary and branch category, and forwards them to subskills to avoid duplicate work. - Smart gating: Skips branch creation when already on a ticket-related branch, skips commits when nothing is uncommitted, and stops cleanly when there is nothing to ship. - Use Case: After finishing a bug fix, say "ship this" and the Skill creates a categorized branch, commits with a summary-based message, pushes, and opens a PR linked to your ticket. ## Quick Start Ship my current changes by creating a branch, committing, pushing, and opening a pull request.

Frequently Asked Questions about ship-changes

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

FAQPage Schema
How do I commit, push, and open a PR in one step?▼

Invoke the shipping workflow with a phrase like "ship this" or "create a PR". It pre-scans your changes, creates a categorized branch if needed, commits, pushes, and opens the pull request automatically.

How does the skill decide the branch name and category?▼

It builds a change summary from uncommitted changes or ahead-of-upstream commits, then derives a category such as feature, fix, refactor, docs, test, chore, perf, build, or ci for the branch name.

What happens if there is nothing to commit or push?▼

The pre-scan checks both uncommitted changes and ahead-of-upstream commits. If both are empty, the workflow stops immediately with a "Nothing to ship" message instead of creating empty branches or PRs.

Does it create a new branch if I am already on a feature branch?▼

No. If the current branch is not master and is already ticket-related, the branch creation step is skipped and the existing branch is reused for committing, pushing, and the PR.

Can I link the pull request to a ticket or set a base branch?▼

Yes. Pass a ticket URL or reference and an optional base branch as arguments. The ticket is forwarded to the PR creation step and the base branch overrides the default PR target.

Related Skills

Explore More Software Engineering Skills→
joeloverbeckjoeloverbeck

spec-to-tickets

Decompose Rulepath gate specs into executable tickets with dependency wiring.

Community
Advanced
basicmachines-cobasicmachines-co
4.0k

fix-pr-issues

Resolves pull request feedback and failed checks, then re-runs the Codex review gate.

Official
Intermediate
svssdevasvssdeva
1

documentation-and-adrs

Record architectural and API decisions as ADRs in docs/decisions.

Community
Intermediate
cogpycogpy

prepare-pr

Rebase GitHub pull requests onto main, apply review fixes, and run automated gates.

Official
Advanced