updatelisted

Run staged cc-enhanced release maintenance on the write side: resolve the real npm latest/next target, pull the clean cli.js, repair patch or prompt drift, promote with native:update, update README/baselines, and verify according to the requested mode. Recommend when the user asks to update, upgrade, patch, repair, or promote cc-enhanced against a release, or names a target version to ship. Read-only inspection (what changed, drift reports, feature inventory) belongs to the release-triage and patch-update workflows; this skill owns repair, promotion, and verification. Supports repair-only, promote-only, and full update flows. Write-side work always targets the newest live version; an older explicit version is comparison-only. Argument is an optional version spec ("latest", "next", "stable", or "X.Y.Z") plus optional pass-through flags. NOT for rollback or workflow docs.
camjac251/cc-enhanced · ★ 6 · AI & Automation · score 76

Install: claude install-skill camjac251/cc-enhanced

# /update [version] [mode flags] Run the staged upstream-release update lifecycle. `$ARGUMENTS` is an optional version spec; defaults to `latest`. Mode flags can include `--inspect-only`, `--repair-only`, `--promote`, `--dry-run`, or `--force`. The process is evidence-first: inspect the live registry and clean bundle before changing source, dry-run patches against the target before promotion, and report patch verification, prompt-surface validity, and prompt drift as separate states. ## Mode Selection - Use **inspect-only** when the user asks "what changed", asks for prompt-drift review first, says no `verify:patches`, says no heavy scripts, or asks to compare the CLI against patches with `rg`/`bat`/`inspect`. - Use **repair-only** when the target clean bundle is known and the user asks to patch or fix broken tags, but has not asked to promote the native binary. - Use **promote/full update** when the user asks to update, upgrade, promote, or run `native:update`. - Use **promote-only** when source patches are already repaired and verified, and the next request is specifically to upgrade the active binary. - Do not edit workflow docs or workflow files unless the user explicitly asks for workflows. ## Steps 1. **Resolve the target from live state.** Do not rely on memory or an older cached bundle. ```bash npm view @anthropic-ai/claude-code version dist-tags --json ``` Use the explicit newest version if `next` is ahead of `latest`, and say so in the update sum