ship-changes

Automate git branching, committing, pushing, PR creation, and cleanup.

1|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/ourchitecture/idp --skill ship-changes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship-changes
Source: https://github.com/ourchitecture/idp/tree/main/.agents/skills/ship-changes
Command: npx skills add https://github.com/ourchitecture/idp --skill ship-changes

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about ship-changes

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

FAQPage Schema
How do I automate creating a git pull request and merging it to main?

Automating a git pull request and merge to main is done by branching, committing with Conventional Commits, pushing to a remote, opening a PR via GitHub MCP, and cleaning up branches end-to-end. This workflow ensures reproducible, auditable shipping.

What is the best way to link a GitHub issue to an automated pull request?

Linking a GitHub issue to an automated pull request requires providing an issue number during the shipping workflow. The process links the issue to the PR, reports progress back to the issue, and can implement the linked issue if no changes are ready.

Does the automated git workflow support Conventional Commits and dry runs?

The automated git workflow supports Conventional Commits for deterministic history and includes dry run capabilities. Dry runs provide safeguards against unintended changes by simulating the branching, pushing, and PR creation process.

Can I configure the remote repository and handle breaking changes in automated PR workflows?

Automated PR workflows support configurable remote options and breaking changes handling. This allows software teams to customize the destination remote and safely manage breaking changes during the end-to-end shipping and merge process.

How does branch cleanup work after merging a pull request to main?

Branch cleanup after merging a pull request to main involves deleting both the remote and local feature branches. This post-merge cleanup is automated, ensuring the repository remains clean after the end-to-end shipping workflow completes.

What is an end-to-end shipping workflow for incremental software changes?

An end-to-end shipping workflow for incremental software changes takes working tree modifications, creates a feature branch, commits, pushes, opens a PR, merges to main, and cleans up branches. It provides a reproducible, auditable process.