ccc-rollback

$ccc-rollback — Revert + Redeploy

CC Commander · $ccc-rollback · Pick target → revert commits → deploy → verify

Use this when production is bad and the safest path is an atomic revert commit followed by a fresh deploy. This workflow preserves history and always redeploys through $ccc-deploy.

Response Shape

Always return these sections:

1. Brand header:

**CC Commander** · $ccc-rollback · Revert + redeploy

1. Current state strip:

Use Bash reads, silent on missing refs:

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:

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

If dirty files are present, warn before any rollback command. Do not proceed until the user confirms.

1. Rollback target picker — AskUserQuestion

question: "What should I roll back to?"
header: "CC Commander Rollback"
multiSelect: false
autocomplete: true
options:
  - label: "Last good commit"
    value: "last-good"
    description: "You provide or confirm the last known good commit sha."
    preview: "Creates revert commits for everything after that commit, then deploys."
  - label: "Specific tag"
    value: "tag"
    description: "Pick a release tag such as v4.0.0-beta.10."
    preview: "Reverts commits after the tag, pushes, then runs $ccc-deploy."
  - label: "N versions back"
    value: "n-back"
    description: "Choose how many release tags back to restore."
    preview: "Finds the older tag, warns about distance, reverts, then deploys."

Target Resolution

Last Good Commit

Ask for the commit sha if it was not supplied in the prompt. Validate it:

git cat-file -e <target-sha>^{commit}
git merge-base --is-ancestor <target-sha> HEAD
git rev-list --count <target-sha>..HEAD

If HEAD is more than 5 commits ahead of the target, warn:

Warning: HEAD is <N> commits ahead of <target>. This may need a surgical rollback instead of reverting everything after the target.