ccc-ship SKILL.md skillA
ccc-ship from kevinzai/commander is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add kevinzai/commander/ccc-ship@git:20261025.55437a6Pins git:20261025.55437a6 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- kevinzai/commander
- Path
commander/cowork-plugin/skills/ccc-ship/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261025.55437a6, committed Oct 25, 2026
- First version recorded
- May 14, 2026
- Size
- 11,001 bytes
- Repository stars
- 6
- License
- MIT
Ship menu: run a parallel pre-flight matrix with a GO, CAUTION or NO-GO scorecard, cut a tagged release with changelog, deploy to a platform, or roll back the last deploy, each gated by a picker. Use when the user says ship it, pre-flight, cut a release, tag a version, or roll back.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# /ccc-ship — Pre-flight, tag, deploy
**CC Commander** · /ccc-ship · pre-flight → tag → deploy, with rollback one pick away
## When to use / when not to
- Use for the whole ship path: check readiness, cut a release, deploy, or undo the last deploy.
- Use `/ccc-deploy-check` for a deeper readiness gate with a rollback plan, `/ccc-deploy` for the deploy alone, and `/ccc-rollback` to revert commits and redeploy.
- Desktop session tools (`mcp__ccd_session__mark_chapter`, `mcp__ccd_session__spawn_task`) are used when present and skipped silently otherwise. In Codex, ask pickers as plain-text questions with the same options and list failures as next steps instead of chips.
## What happens
### 1. Read ship readiness
Run in one Bash call, silent on failure:
```bash
git rev-parse --abbrev-ref HEAD
git status --porcelain | wc -l
git rev-list --count main..HEAD 2>/dev/null
test -f package.json && node -p "require('./package.json').version"
test -f .github/workflows/ci.yml && echo yes
ls -t tasks/ship/preflight-*.md 2>/dev/null | head -1
```
Render one line:
> 📊 Branch: `<branch>` · <N> commits ahead · <X> uncommitted · current version: `<ver>` · CI: `<yes/no>`
…Read the whole file at its exact version.
How to install
mdr add kevinzai/commander/ccc-ship@sha256:50ba89b60cf786c6The line at the top of this page pins the label git:20261025.55437a6, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_vz4zurjooildnphj)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between May 14, 2026 and Oct 25, 2026, about one every 41 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261025.55437a6 latest | 2026-10-25 | 55437a6 | 11,001 B | A | view · diff |
| git:20261025.7eae921 | 2026-10-25 | 7eae921 | 10,988 B | A | view · diff |
| git:20261013.fbe187d | 2026-10-13 | fbe187d | 11,015 B | A | view · diff |
| git:20260707.947ab2f | 2026-07-07 | 947ab2f | 9,641 B | A | view · diff |
| git:20260514.2648602 | 2026-05-14 | 2648602 | 9,472 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (11001 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
kevinzai/commander · 6 stars · license MIT · pushed 2026-11-08 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_vz4zurjooildnphj GET https://markdownregistry.com/api/v1/resolve?ref=kevinzai/commander/ccc-ship GET https://markdownregistry.com/api/v1/blob/50ba89b60cf786c696e2d9533e0f7983b0771de9bd9cf1b3a25aa83f588d9a03
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from kevinzai/commander
Every file in kevinzai/commander