cc-updatelisted
Install: claude install-skill WingedGuardian/GENesis-AGI
# CC Update — start from the canonical source, don't rediscover
Genesis's Claude Code update process is fully standardized. This skill exists so a session
**executes** that process instead of re-deriving it (grep archaeology every time). If you find
yourself hunting for where the pin lives or how the host updates, STOP and read the doc.
## Authoritative source — read these FIRST
- `docs/reference/cc-compatibility.md` → **§Updating Claude Code (host + container)** (the exact
steps) and **§CC Update Evaluation Checklist** (the 8-lens impact eval).
- The pin is the single source of truth: `CC_VERSION` (+ `NODE_MAJOR`) in
`scripts/lib/cc_version.sh`.
## The process in one breath — step numbers MATCH §Updating Claude Code in the doc
> Deliberately the same numbering in both files: "step 4" means the same thing in each. The doc is
> authoritative for detail; this is the one-breath version. If a number here disagrees with the
> doc, the doc wins — and that disagreement is a bug worth fixing rather than working around.
**Pick the target before anything else.** `npm view @anthropic-ai/claude-code version` gives
`latest`; use an explicit older version if you are deliberately not chasing latest. Every step below
is defined over `(pinned, target]`, so nothing can begin until `target` is fixed — and re-picking it
later restarts the procedure (step 5).
> ### ⛔ GATE — FULL CHANGELOG READ. MANDATORY, NO EXCEPTIONS. (part of step 1, before any triage)
> **Read EVERY release entry in