ccb-github

Automate CCB release preparation, GitHub publishing, and npm registry verification.

3.5k|342|Updated Oct 25, 2025
One-click install
npx skills add https://github.com/bfly123/claude_code_bridge --skill ccb-github
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ccb-github
Source: https://github.com/bfly123/claude_code_bridge/tree/main/dev_tools/skills/ccb-github
Command: npx skills add https://github.com/bfly123/claude_code_bridge --skill ccb-github

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

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.

Frequently Asked Questions about ccb-github

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify a GitHub release is fully published?

Run the bundled checker with the published phase and a wait window, for example check_release_state.py --phase published --wait-seconds 1800. It validates the tag, GitHub Release page, release assets, SHA256SUMS, workflow runs, and default-branch README state.

How do I keep version numbers consistent across a release?

Update VERSION, the ccb VERSION constant, package.json, CHANGELOG.md, and both README files together in one release commit. The prepare-phase checker fails if any of these surfaces disagree with the intended release version.

Does the release checker modify my repository?

No, the checker is read-only and only reports issues with suggested fixes. Git writes, tag operations, GitHub Release edits, and workflow reruns are explicit actions performed separately in the documented publish sequence.

Why does the GitHub homepage still show an old version after release?

GitHub renders the README from the default branch, not from release tags. Merge the release documentation branch into the default branch and push it, then rerun the published-phase check to confirm the homepage updated.

What happens if npm Trusted Publishing is not configured?

The npm publish workflow will fail with authentication errors. Configure the npm package with the correct owner, repository, workflow filename npm-publish.yml, blank environment, and allowed npm publish action, then rerun the Npm Publish workflow for the release tag.