Shipping a PR is the same sequence every time and yet teams botch it on a regular basis. Forgot to merge main first, tests fail because of an unrelated upstream change. Forgot the version bump. Pushed without running the full test suite. Created the PR without the right description. The sequence is mechanical, the failures are common, and each one is a small irritation that adds up across a team.
The /relay-ship skill is the end-to-end ship workflow. Merge the base branch into the feature branch. Run tests. Audit coverage to catch regressions. Review the diff for accidental changes. Bump version if applicable. Commit with a structured message. Push. Create the PR with a generated description and the test plan. The skill is non-interactive by default; it stops only for real judgment calls (test failure that needs attention, conflicting merge, ambiguous version bump).
What ship workflow covers
Eight steps. 1: Merge the latest main into the feature branch (rebase or merge depending on team policy). 2: Run the full test suite. 3: Audit test coverage if a coverage gate is configured. 4: Review the diff against the original commits to flag scope creep. 5: Bump the version if the project uses semver. 6: Commit with a structured message. 7: Push the branch. 8: Create the PR with a generated title, description, and test plan.
The single most useful checkpoint is the diff review. /relay-ship surfaces unrelated changes (logging tweaks, formatting drift, unintended file additions) before the PR is created so they can be removed or split rather than asked about in review.
Tonone's /relay-ship skill runs the end-to-end ship workflow non-interactively, stopping only for real judgment calls.
When to use /relay-ship
/relay-ship is the right call when a feature branch is ready to merge and the team wants the mechanical steps automated. Skip it for work-in-progress commits or for branches that need design review before PR creation.
Related skills
Install
/relay-ship ships with the Relay agent in Tonone for Claude Code.
1. Add to marketplace
2. Install Relay
Frequently asked questions
- What does /relay-ship do?
- It runs the end-to-end ship workflow: merge base into feature branch, run tests, review diff, bump version, commit, push, and create PR with description.
- Is /relay-ship interactive?
- Non-interactive by default. It stops only for real judgment calls (test failure, conflicting merge, ambiguous version bump).
- How do I install /relay-ship?
- Install Tonone for Claude Code via tonone.ai/get-started. Tonone is free and MIT-licensed.