What happens if bin/ci fails?

Stop the process, show the failure output, and do not push or create a PR. Fix locally and re-run bin/ci.

Can I customize the commit message?

Yes. Provide an ARGUMENTS value for the commit message; otherwise craft a descriptive message manually.

How is the PR created and what will I see?

After a successful bin/ci run, gh pr create will be used to open the PR. The response should include the PR URL and a brief summary such as the number of files changed.

ship

Scanned

npx machina-cli add skill robzolkos/zolkos-agent-skills/ship --openclaw

Files (1)

SKILL.md

1.2 KB

Context

Current git status: !git status
Current git diff (staged and unstaged changes): !git diff HEAD
Current branch: !git branch --show-current
Recent commits: !git log --oneline -10

Your task

Ship the current changes by following these steps in order:

1. Create a branch if needed

If on master, create and checkout a new descriptive branch based on the changes.

2. Commit

Stage all changed files and create a single commit with an appropriate message. If $ARGUMENTS is provided, use it as the commit message.

3. Run CI

Run bin/ci and wait for it to complete. This is mandatory — do not skip it.

If bin/ci fails: stop here. Show the failure output and suggest fixes. Do NOT push or create a PR.
If bin/ci passes: continue to step 4.

4. Open a PR

bin/ci already pushed the branch to origin. Create a pull request using gh pr create and return the PR URL and a brief summary of files changed eg 2 Files Changed

Source

git clone https://github.com/robzolkos/zolkos-agent-skills/blob/master/skills/ship/SKILL.mdView on GitHub

Overview

This skill automates shipping changes by creating a branch when needed, committing with a message (or ARGUMENTS), running bin/ci, and opening a PR via gh pr create when CI succeeds. It enforces CI validation before merging and keeps the shipping process consistent.

How This Skill Works

Follow the steps in order: if you’re on master, create and switch to a descriptive branch. Stage all changes and commit (use ARGUMENTS for the message if provided). Run bin/ci and, only if it passes, push the branch and create a PR with gh pr create; the skill returns the PR URL and a brief summary of changed files.

When to Use It

You’ve completed a feature or fix and are ready to ship to main
CI must pass before changes are merged
You want a single, descriptive commit message or to use provided ARGUMENTS
You’re on master and need to create a descriptive branch for shipping
You want an automated PR creation with a concise summary of changed files

Quick Start

Step 1: If on master, git checkout -b feature/your-change and switch to it
Step 2: git add -A && git commit -m "Your message" (or use $ARGUMENTS as the message)
Step 3: Run bin/ci; if it passes, push and run gh pr create to obtain the PR URL and summary

Best Practices

Provide a clear commit message or use ARGUMENTS to describe the change
Always run bin/ci and require a successful result before PR
Keep the ship process as a single, cohesive commit when appropriate
Create a descriptive branch when shipping from master
Include a brief PR description listing affected files in the PR

Example Use Cases

Ship a bugfix: create feature/bugfix-login, commit with message, run bin/ci, and open PR after CI passes
Ship a UI tweak: update two files, pass CI, and generate PR with summary of files changed
Upgrade a dependency: commit changes, run CI, and PR once green
Refactor a module: single commit highlighting refactor, CI passes, PR created
Hotfix that requires validation: branch off master, CI validate, PR open with changes clearly described

Frequently Asked Questions

Add this skill to your agents