ccc-rollback SKILL.md skillB

ccc-rollback 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-rollback@git:20261013.fbe187d

Pins git:20261013.fbe187d in mdr.lock. Pin the fingerprint instead.

Audit grade: B, 16 of 17 checks passed
Kind: SKILL.md skill
Repository: kevinzai/commander
Path: commander/cowork-plugin-codex/skills/ccc-rollback/SKILL.md
Versions recorded: 5
Latest version: git:20261013.fbe187d, committed Oct 13, 2026
First version recorded: May 1, 2026
Size: 8,049 bytes
Repository stars: 6
License: MIT

Roll production back by picking a known-good commit or tag, creating atomic git revert commits, pushing them, redeploying through the $ccc-deploy runners, and verifying health. Use when a deploy is bad, production is broken, or the user asks to revert or roll back a release.

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-rollback — Revert and redeploy

**CC Commander** · $ccc-rollback · pick target → revert commits → push → redeploy → verify

## When to use / when not to

- Use when production is bad and the safest fix is a revert commit followed by a fresh deploy. History is preserved; nothing is rewritten.
- For an instant platform-level rollback with no git change (`vercel rollback`, `fly releases rollback`, `wrangler rollback`), use `$ccc-ship rollback` instead.
- In Codex, ask each picker below as a plain-text question with the same options.

## What happens

### 1. Read the current state

Run in one Bash call; a missing ref is not an error:

```bash
git rev-parse --abbrev-ref HEAD
git rev-parse --short HEAD
git status --short
git tag --sort=-creatordate | head -10
git log --oneline --decorate -12
```

Render one line:

```markdown
Branch: `<branch>` · HEAD: `<short-sha>` · dirty files: `<N>` · latest tag: `<tag-or-none>`
```

If dirty files are present, ask with AskUserQuestion before any rollback command: "🟢 Stop — I'll commit or stash first" or "Continue with a dirty tree" (the revert may mix with uncommitted work). Do not proceed without an answer.
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add kevinzai/commander/ccc-rollback@sha256:9cf9d442d569c84e

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_7jakj3jz2nnizqbs.svg)](https://markdownregistry.com/a/art_7jakj3jz2nnizqbs)

1 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 5 versions of this file, between May 1, 2026 and Oct 13, 2026, about one every 41 days. Its first recorded version is graded A and its latest B.

version	committed	commit	size	audit
git:20261013.fbe187d latest	2026-10-13	fbe187d	8,049 B	B	view · diff
git:20260722.9d3ab82	2026-07-22	9d3ab82	6,091 B	A	view · diff
git:20260707.947ab2f	2026-07-07	947ab2f	5,959 B	A	view · diff
git:20260514.2648602	2026-05-14	2648602	5,790 B	A	view · diff
git:20260501.27abf7b	2026-05-01	27abf7b	5,805 B	A	view

Audit of the latest version

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

fail: No instruction to read or print local credentials (matched: print secrets or `.env)
pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (8049 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 base64 blob over 200 characters
pass: No link to a raw IP address
pass: No script tag

Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.

Source

GitHub

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

API

GET https://markdownregistry.com/api/v1/artifacts/art_7jakj3jz2nnizqbs
GET https://markdownregistry.com/api/v1/resolve?ref=kevinzai/commander/ccc-rollback
GET https://markdownregistry.com/api/v1/blob/9cf9d442d569c84ee30c84f5ca5bed4f600a8552ed5fa41ff7ca5e5b5b5d6f51

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