What problem does it solve?
Ship Changes automates the end-to-end workflow to take changes from your working tree, create a feature branch, commit with Conventional Commits, push to a remote, open a PR via the GitHub MCP server, and merge into main, followed by remote branch cleanup and local branch cleanup. When an issue_number is provided and the tree has no ready-to-ship implementation, it can implement the linked issue first and then ship. This skill enables a reproducible, auditable workflow for shipping incremental changes to main.
Core Features & Use Cases
- End-to-end shipping: review changes, branch, commit, push, open PR, merge to main, and clean up branches.
- Issue-aware shipping: if issue_number is provided, link it to the PR and issue, with progress reported back to the issue.
- Dry-run and safeguards: supports dry_run, breaking changes handling, and deterministic commit history through small commits.
Quick Start
Run the ship-changes skill to ship pending changes from your working tree to main via an automated PR workflow.