ccc-upgrade

$ccc-upgrade — Vendor Submodule Updater

🔎 Looking to update the CC Commander plugin itself (not this repo's vendor submodules)? That's $ccc-update — a different, end-user-facing tool with a similarly-spelled name. This skill is maintainer-only.

⚠️ Run only from the CC Commander repo root. Verify pwd ends in /cc-commander (or your fork's name) and ls .claude-plugin/marketplace.json succeeds. Running this skill in the wrong cwd would touch unrelated submodules.

Interactive workflow that audits the 19+ vendor submodules under vendor/, surfaces what changed upstream, lets the user pick which to update via AskUserQuestion, then runs the update + test + commit cycle one submodule at a time.

Similar in spirit to $ccc-doctor (read-only diagnostic) — this one writes (commits per submodule) but only after explicit user approval.

When to fire

User types $ccc-upgrade, or says any of:

• "update vendors"
• "refresh submodules"
• "pull latest vendor changes"
• "sync the ecosystem"
• "are any vendors out of date"
• "check vendor drift"

Args:

• --check — read-only audit (no fetch, no update, no commit)
• --all — skip the picker and update every submodule with available updates

Steps (always in this order)

1. Locate the repo root + sanity check

Resolve repo root via git rev-parse --show-toplevel. If that fails, output: "Not in a git repo — $ccc-upgrade only works inside the cc-commander checkout." and exit.

Before proceeding, verify you are at the cc-commander repo root:

# Guard: must be at the cc-commander repo root
if [ ! -f ".claude-plugin/marketplace.json" ]; then
  echo "❌ Not at cc-commander repo root. Refusing to update vendor submodules."
  exit 1
fi

If the guard fails, output the error message and exit.

Verify vendor/ exists:

test -d vendor || echo "no-vendor-dir"

If missing, output: "No vendor/ directory at repo root — nothing to upgrade." and exit.

2. List submodules

git submodule status