Home / kevinzai / commander · GitHub

ccc-deploy-check SKILL.md skillA

ccc-deploy-check from kevinzai/commander is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned

mdr add kevinzai/commander/ccc-deploy-check@git:20261013.fbe187d

Pins git:20261013.fbe187d 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-codex/skills/ccc-deploy-check/SKILL.md
Versions recorded: 5
Latest version: git:20261013.fbe187d, committed Oct 13, 2026
First version recorded: May 14, 2026
Size: 9,120 bytes
Repository stars: 6
License: MIT

Pre-deploy readiness gate: tests, build, debug logs, secrets, TODOs, lockfile and destructive-migration checks with a GO, CAUTION or NO-GO verdict, plus risk and rollback plan in power mode. Use when asking ready to ship, should I deploy, is it safe, deploy check, or pre-deploy.

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-deploy-check — Pre-deploy readiness gate

**CC Commander** · $ccc-deploy-check · a GO, CAUTION or NO-GO verdict before anything goes live

Placeholders like ~~CI/CD and ~~monitoring refer to connected tools, which are opt-in and absent by default. See [CONNECTORS.md](../../CONNECTORS.md).

## When to use / when not to

- Use before any deploy. Quick mode runs by default; power mode adds risk assessment and a rollback plan.
- This skill only reads. To deploy, use `$ccc-deploy`; for the full ship menu (pre-flight matrix, release tagging), use `$ccc-ship`.
- In Codex, ask the picker as a plain-text question; run the power-mode verifier with `codex exec` in a fresh session, read-only.

## What happens

### 1. Resolve the base and changed files

```bash
BASE_REF=$(git symbolic-ref --short refs/remotes/origin/HEAD 2>/dev/null || echo main)
BASE=$(git merge-base HEAD "$BASE_REF")
git diff --name-only --diff-filter=ACM "$BASE"...HEAD
git diff --shortstat "$BASE"...HEAD
```

If there is no remote or no diff, check the working tree against `HEAD` instead and say so.

### 2. Quick mode (default)

Run every check, no questions. Report each as PASS, WARN or FAIL.
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add kevinzai/commander/ccc-deploy-check@sha256:f0d7e10acb56271c

The line at the top of this page pins the label git:20261013.fbe187d, 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.

Badge

[![mdr](https://markdownregistry.com/badge/art_7gzuum3giogsytjc.svg)](https://markdownregistry.com/a/art_7gzuum3giogsytjc)

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 13, 2026, about one every 38 days.

version	committed	commit	size	audit
git:20261013.fbe187d latest	2026-10-13	fbe187d	9,120 B	A	view · diff
git:20260722.9d3ab82	2026-07-22	9d3ab82	5,355 B	A	view · diff
git:20260707.947ab2f	2026-07-07	947ab2f	5,223 B	A	view · diff
git:20260701.1f4accc	2026-07-01	1f4accc	5,054 B	A	view · diff
git:20260514.2648602	2026-05-14	2648602	5,026 B	A	view

Audit of the latest version

A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.

pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (9120 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

GitHub

kevinzai/commander · 6 stars · license MIT · pushed 2026-11-08 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_7gzuum3giogsytjc
GET https://markdownregistry.com/api/v1/resolve?ref=kevinzai/commander/ccc-deploy-check
GET https://markdownregistry.com/api/v1/blob/f0d7e10acb56271c687acdf46d04b53a2359f3d9dc6c90c0f7d3c5e612a38778

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

mintlify SKILL.md skill

kevinzai/commander · .agents/skills/mintlify/SKILL.md · Build and maintain documentation sites with Mintlify. Use when

v1.0 · audit A · 6 stars

.cursorrules Cursor rule

kevinzai/commander · .cursorrules

git:20260327.b10b207 · audit A · 6 stars

AGENTS.md AGENTS.md file

kevinzai/commander · AGENTS.md