Scaffold the four files for a new cc-enhanced patch (src/patches/<tag>.ts, <tag>.test.ts, the export-barrel entry, and the BY_TAG metadata record). Scaffold-only; the rest of the procedure (prompt-surface rules, count sync, clean-bundle inspection, and native verification) lives in CLAUDE.md > Adding Patches. Recommend by name when the user wants to add a new patch behavior. Triggers on "new patch", "add a patch", "scaffold a patch", "create a patch for X", "start a patch". Argument is the patch tag (e.g. "my-feature"). If the tag, one-line purpose, or group (Prompt, Tooling, Agent, System, UX, Metadata) is missing, ask before scaffolding. NOT for editing an existing patch directly and NOT for end-to-end implementation; this skill stops at scaffolding and hands off to the implementation workflow.
Run staged cc-enhanced release maintenance: resolve the real npm latest/next target, pull the clean cli.js, inspect bundle drift, repair patch or prompt drift, optionally promote with native:update, update README/baselines, and verify according to the requested mode. Recommend after an upstream Claude Code release or when the user asks what changed, to inspect prompt drift, patch a release, update/upgrade Claude Code, promote, or names a target version. Supports inspect-only/no-heavy-verifier, repair-only, promote-only, and full update flows. Argument is an optional version spec ("latest", "next", "stable", or "X.Y.Z") plus optional pass-through flags. NOT for rollback or workflow docs.