Ship

Skill robzolkos/zolkos-agent-skills/skills/ship

Commit, run bin/ci, and open a PR if CI passes. Use when ready to ship changes.From its SKILL.md

Install

npx -y skills add robzolkos/zolkos-agent-skills --skill ship

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.2 KB, 258 tokens by cl100k_base, as published. Nobody here has run it

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

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most ship operate skills give in 258 tokens

Counted across 779 of the 1,178 authors here whose files we hold, read 2026-08-07

Document a rollback plan before deploymentin 41 of 779, across 22 files
Update the changelogin 21 of 779, across 19 files
Run the test suitein 20 of 779
Create an annotated git tagin 20 of 779
Clean up feature flags after full rolloutin 18 of 779, across 10 files
Verify deployment health after launchin 18 of 779, across 10 files
Test both feature flag statesin 17 of 779, across 9 files
Verify the working tree is cleanin 17 of 779
Make database migrations backward-compatiblein 16 of 779, across 8 files
Set up error monitoring before launchin 15 of 779, across 7 files
Monitor metrics at each rollout stagein 14 of 779, across 5 files
Create a GitHub releasein 14 of 779

Said here and by no other author read

create a descriptive branch if on master
use provided arguments as commit message
run bin/ci
wait for bin/ci to complete
create a pull request on passing ci
return the pull request url

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.