What problem does it solve?
Releasing the CCB project requires keeping version files, changelogs, bilingual READMEs, Git tags, GitHub Releases, release assets, GitHub Actions workflows, and npm registry state perfectly aligned; this Skill automates that audit and publish workflow so nothing drifts out of sync.
Core Features & Use Cases
- Release Surface Auditing: Run the bundled read-only checker in dev, prepare, or published phases to detect version mismatches, stale README badges, missing tags, and incomplete release assets.
- Guided Publish Sequence: Follow a strict ordered workflow covering commits, branch merges, tag creation, GitHub Release pages, Release Artifacts assets, and npm Trusted Publishing.
- Recovery Runbook: Diagnose and fix common failures such as missing release assets, tag SHA mismatches, npm Trusted Publisher misconfiguration, and stale homepage READMEs.
- Use Case: After bumping CCB to a new version, ask the agent to prepare and publish the release; it updates VERSION, package.json, CHANGELOG.md, and both READMEs, runs local verification, pushes the tag, waits for workflows, and confirms npm registry state.
Quick Start
Ask the agent to run the release checker in prepare phase and fix every reported issue before tagging the next CCB release.