Agent skill

Cb Release

How a Circuit Breaker release is cut, approved, published and followed up — the candidate→approval→promote flow in release.yml, the release environment gate, the make release- targets, the…

MITAuto-check passedDevelopment

Install Cb Release

skills CLI

$ npx skills add BlkLeg/CircuitBreaker --skill cb-release -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install BlkLeg/CircuitBreaker cb-release --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/BlkLeg/CircuitBreaker.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/cb-release .claude/skills/cb-release && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "cb-release" agent skill from https://github.com/BlkLeg/CircuitBreaker/tree/main/.claude/skills/cb-release into .claude/skills/cb-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cb-release", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/BlkLeg/CircuitBreaker/tree/main/.claude/skills/cb-release

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add BlkLeg/CircuitBreaker --skill cb-release -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install BlkLeg/CircuitBreaker cb-release --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/BlkLeg/CircuitBreaker.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/cb-release .agents/skills/cb-release && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "cb-release" agent skill from https://github.com/BlkLeg/CircuitBreaker/tree/main/.claude/skills/cb-release into .agents/skills/cb-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cb-release", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add BlkLeg/CircuitBreaker --skill cb-release -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install BlkLeg/CircuitBreaker cb-release --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/BlkLeg/CircuitBreaker.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/cb-release .cursor/skills/cb-release && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "cb-release" agent skill from https://github.com/BlkLeg/CircuitBreaker/tree/main/.claude/skills/cb-release into .cursor/skills/cb-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cb-release", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/BlkLeg/CircuitBreaker.git --path .claude/skills/cb-release

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add BlkLeg/CircuitBreaker --skill cb-release -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install BlkLeg/CircuitBreaker cb-release --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/BlkLeg/CircuitBreaker.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/cb-release .gemini/skills/cb-release && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "cb-release" agent skill from https://github.com/BlkLeg/CircuitBreaker/tree/main/.claude/skills/cb-release into .gemini/skills/cb-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cb-release", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install BlkLeg/CircuitBreaker cb-release

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add BlkLeg/CircuitBreaker --skill cb-release -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/BlkLeg/CircuitBreaker.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/cb-release .github/skills/cb-release && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "cb-release" agent skill from https://github.com/BlkLeg/CircuitBreaker/tree/main/.claude/skills/cb-release into .github/skills/cb-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cb-release", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add BlkLeg/CircuitBreaker --skill cb-release -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install BlkLeg/CircuitBreaker cb-release --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/BlkLeg/CircuitBreaker.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/cb-release .opencode/skills/cb-release && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "cb-release" agent skill from https://github.com/BlkLeg/CircuitBreaker/tree/main/.claude/skills/cb-release into .opencode/skills/cb-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cb-release", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: cb-release
GitHub stars: 201
Token cost: ~1.8k tokens
SKILL.md length: 776 words
Files: 1
Skills in repo: 6
Repo updated: Oct 5, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

How a Circuit Breaker release is cut, approved, published and followed up — the candidate→approval→promote flow in release.yml, the release environment gate, the make release- targets, the…

Works in 8 steps: Never push a v* tag. A hand-pushed tag… → The release environment must exist with… → promote-verify needs contents: write… → …
Promote a version
SKILL.md covers The flow, Rules that each cost a failed…, Diagnosing a red Release run and What a release does NOT prove, plus 1 more section
Calls make, git and gh; needs GITHUB_TOKEN

What it does

Cb Release is an agent skill from BlkLeg/CircuitBreaker. How a Circuit Breaker release is cut, approved, published and followed up — the candidate→approval→promote flow in release.yml, the release environment gate, the make release- targets, the post-release follow-up PR that bumps VERSION and rotates the CHANGELOG, and how to diagnose and recover a failed release. Use this whenever the user asks to tag, release, ship, publish or promote a version, bump VERSION, edit CHANGELOG release headings, touch release.yml or release-followup.yml, clean up draft releases, or when…

Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Changelog and release notes. It works with GitHub. The repository describes itself as: Bring your homelab to life. A self-hosted IPAM and service mapper that visualizes complex hardware, compute, and network relationships in real-time. The licence is MIT.

When your agent uses it

Promote a version
Edit CHANGELOG release headings
Touch release.yml
Release-followup.yml

Example prompts

“/cb-release”

Requirements

Node.js
A credential in GITHUB_TOKEN

Workflow steps

8 steps, taken from the first numbered list in SKILL.md.

Never push a v* tag. A hand-pushed tag runs only tag-verify, which
The release environment must exist with a required reviewer. GitHub
promote-verify needs contents: write although it only reads. GitHub
Promote runs on the candidate's exact commit. promote-verify
A tag created by GITHUB_TOKEN fires no push: tags: workflow, and a
VERSION is the only hand-edited version (GOV-09). Everything else is
CHANGELOG headings: released versions read ## [X.Y.Z] — YYYY-MM-DD
Prereleases (X.Y.Z-rc.N) have no mechanical next version

What it can do on your machine

Read from SKILL.md and the folder at commit fc44f2e. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- make
- git
- gh
- npx
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, gh and npx, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
- GITHUB_TOKEN
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Cb Release loads about 1.8k tokens when it runs. Until then it costs about 150 tokens; SKILL.md has 776 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~150
When it runs · the whole SKILL.md, loaded when a task matches: ~1.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from BlkLeg/CircuitBreaker at commit fc44f2e, republished under its MIT licence (© BlkLeg). 776 words, ~1,815 tokens.

Download SKILL.mdSave it as .claude/skills/cb-release/SKILL.md (or your agent's skills folder).

name: cb-release
description: How a Circuit Breaker release is cut, approved, published and followed up — the candidate→approval→promote flow in release.yml, the `release` environment gate, the make release-* targets, the post-release follow-up PR that bumps VERSION and rotates the CHANGELOG, and how to diagnose and recover a failed release. Use this whenever the user asks to tag, release, ship, publish or promote a version, bump VERSION, edit CHANGELOG release headings, touch release.yml or release-followup.yml, clean up draft releases, or when a Release run is red. Never push a v* tag by hand — read this first.

Circuit Breaker — Releasing

A release is one dispatch and one human approval. The tag is the last thing that happens, created when the draft is published. Nobody makes a tag by hand.

The flow

make release-candidate            (from main, HEAD must be on origin)
  └─ release.yml channel=candidate promote=true
       gate → build → artifact-smoke → installer-journey (6 distros)
       → image (amd64+arm64) → runtime-parity → Stage Draft Release
       → Discord: "vX draft staged, waiting for you"
       → release-environment-guard, promote-verify
       → promote  ⏸ waits for approval on the `release` environment
                  (Review deployments on the run page, or GitHub mobile)
       → publish draft = tag created → post-publish verifies the
         published assets, dispatches e2e.yml and release-followup.yml
       → Discord: "vX is published"
release-followup.yml (on dev)
  └─ bumps VERSION to next patch, dates the CHANGELOG heading, opens
     `## [next] — unreleased`, deletes stale drafts ≤ vX, opens a PR
     into dev, dispatches the required checks onto it

Target	Does
`make release-candidate`	The normal path: build, gate, stage, then wait for approval and publish
`make release-stage-only`	Stop at the draft (`promote=false`), e.g. to soak it for a while
`make release-promote`	Publish an already-staged draft (`channel=stable`). Must run on the same commit the draft was built from

Approving is the moment to soak if you want to: gh release download vX --pattern '*linux_amd64.tar.gz' then install.sh --local-bundle <tarball> --unattended --no-tls. The approval can wait days; nothing re-builds.

Rules that each cost a failed release to learn

Never push a v* tag. A hand-pushed tag runs only tag-verify, which fails on purpose and prints the delete command. If you created a local tag, git tag -d vX.
The release environment must exist with a required reviewer. GitHub silently creates a missing environment unprotected and runs straight through, which would publish without anyone approving. release-environment-guard fails the run in its first minute unless the required_reviewers rule is there. "Prevent self-review" must stay off while there is only one maintainer, or nobody can approve.
promote-verify needs contents: write although it only reads. GitHub hides draft releases from tokens without push access; with read, gh release view says "release not found" for a draft that exists (v0.4.4, PR #161). test_jobs_that_read_the_draft_can_see_it guards this.
Promote runs on the candidate's exact commit. promote-verify compares candidate.json's commit with GITHUB_SHA. So a fix to release.yml itself cannot promote an existing draft: merge the fix, then cut a new candidate from the new main commit. The candidate job deletes and replaces the old draft of the same version.
A tag created by GITHUB_TOKEN fires no push: tags: workflow, and a release it publishes fires no release: published workflow. That is why post-publish dispatches e2e.yml and release-followup.yml explicitly — workflow_dispatch is the one event GITHUB_TOKEN can start.
VERSION is the only hand-edited version (GOV-09). Everything else is generated by scripts/check_version_parity.py --write (make version-sync). The follow-up PR does both for you after each release.
CHANGELOG headings: released versions read ## [X.Y.Z] — YYYY-MM-DD (UTC publish date); the next one reads ## [X.Y.Z] — unreleased. scripts/release_checklist.py requires a ## [VERSION] heading before a draft may be staged. scripts/post_release_bump.py does the rotation; a version bump must never rename the previous section (that is how the 0.4.3 notes were lost into 0.4.4).
Prereleases (X.Y.Z-rc.N) have no mechanical next version: release-followup fails on them by design. Bump VERSION by hand after an rc.

Show full SKILL.md (343 more words)Show less

Diagnosing a red Release run

Start from the failing job, not the run conclusion:

Failing job	Usually means	Do
Derive Version	`version` input ≠ VERSION at that ref	Dispatch on the right ref or fix the input
release-environment-guard	Environment missing or lost its reviewer	Settings → Environments → `release` → Required reviewers
Verify the candidate before promoting: "has no draft to promote"	No draft for VERSION, or the token cannot see drafts	`gh release list`; check rule 3
… "the draft was built from X"	Promote dispatched on a different commit	Dispatch on the candidate's commit, or cut a new candidate
… "no longer matches candidate.json" / digest moved	Draft assets or the `:X-candidate` image changed after staging	Re-run the candidate; never hand-edit a draft
Stage Draft Release: "already published"	VERSION was not bumped after the last release	Merge the follow-up PR (or bump VERSION)
post-publish	The published release is broken (asset name, checksum, selftest, API discovery)	Treat as an incident: users can download it now
tag-verify	Someone pushed a tag	`git push origin :refs/tags/vX`

gh run view <id> --log-failed | tail -60 gets the error. Per CLAUDE.md, never call a red release check flaky or stale without reproducing it.

What a release does NOT prove

The release gates run artifact-smoke, installer-journey and runtime-parity, which cover packaging. They do not run the browser E2E or the composed agent E2E (quarantined as QUAR-001, issue #162). A release after a frontend dependency bump or an agent change still needs npx playwright test or make e2e-local locally first — see CLAUDE.md "What the gates do NOT cover".

Touching release.yml

Read tests/build/test_release_publication_is_gated.py, test_release_approval_gate.py, test_workflow_job_graph.py and test_release_paths_run_before_the_tag.py first; they encode the graph.
No continue-on-error and no always() on release jobs. Conditions use !cancelled() && !failure() plus explicit needs.<job>.result == 'success'.
Every ${{ }} reaches shell through env:, quoted.
New workflow_dispatch inputs need the # checkov:skip=CKV_GHA_7 comment or the required Checkov check goes red.
Only promote may declare environment: release.
The change only takes effect for releases dispatched from a ref that contains it; a fix on dev does nothing until it reaches main.

Notifications and the other bots are described in cb-automation.

Files

Just SKILL.md in .claude/skills/cb-release of BlkLeg/CircuitBreaker.

Open the folder on GitHubat commit fc44f2e

Compare with similar skills

Cb Release next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Cb Release compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Cb Release this skillBlkLeg/CircuitBreaker	201	—	~1.8k	Automated safety check: Pass	MIT	2 days ago
Cutting A ReleaseTriliumNext/Trilium	38k	—	~3.2k	Automated safety check: Pass	AGPL-3.0	today
Mole CLI Release Flowtw93/Mole	70k	—	~2.5k	Automated safety check: Pass	GPL-3.0	today
Draft Release Notesjamiepine/voicebox	57k	—	~941	Automated safety check: Pass	MIT	yesterday
Mole Release Notes Publishertw93/Mole	70k	—	~1.9k	Automated safety check: Pass	GPL-3.0	today
Release Bumpjamiepine/voicebox	57k	—	~1.1k	Automated safety check: Pass	MIT	yesterday

Similar skills

Cutting A Release
TriliumNext/Trilium
A skill your agent uses when cutting, preparing, or debugging a Trilium release — bumping the monorepo version, tagging, or diagnosing a failed "Release" workflow run.
38k GitHub stars~3.2k tokensUpdated today
DevelopmentAuto-check passed
Mole CLI Release Flow
tw93/Mole
Runbook for assessing and executing a Mole CLI release: distribution channels, pre-flight checks, capital-V tags, build artifacts and the handoff to curated release notes.
70k GitHub stars~2.5k tokensUpdated today
DevelopmentAuto-check passed
Draft Release Notes
jamiepine/voicebox
Writes or refreshes the Unreleased section of CHANGELOG.md as a themed narrative built from the commits, PRs and diff since the last version tag.
57k GitHub stars~941 tokensUpdated yesterday
DevelopmentAuto-check passed
Mole Release Notes Publisher
tw93/Mole
Publishes curated, bilingual release notes for an existing Mole version tag with gh release edit, including contributor thanks and reactions, after the release workflow finishes.
70k GitHub stars~1.9k tokensUpdated today
DevelopmentAuto-check passed
Release Bump
jamiepine/voicebox
Ends a release cycle by moving the Unreleased changelog notes under a dated version heading, bumping version files with bumpversion and tagging the commit.
57k GitHub stars~1.1k tokensUpdated yesterday
DevelopmentAuto-check passed
Cut Release
jfernandez/bpftop
Cut a new versioned release of bpftop — pick the version, open a version-bump PR, sign-tag the merge commit on main, and draft GitHub release notes in the project's established format.
2.7k GitHub stars~2k tokensUpdated 1 mo ago
DevelopmentAuto-check passed

Questions about Cb Release

What does Cb Release do?

How a Circuit Breaker release is cut, approved, published and followed up — the candidate→approval→promote flow in release.yml, the release environment gate, the make release- targets, the…. Cb Release is an agent skill from BlkLeg/CircuitBreaker.yml, the release environment gate, the make release- targets, the post-release follow-up PR that bumps VERSION and rotates the CHANGELOG, and how to diagnose and recover a failed release.

When should I use Cb Release?

Cb Release fits situations like: promote a version; edit CHANGELOG release headings; touch release.yml; release-followup.yml.

How do I install Cb Release in Claude Code?

Run `npx skills add BlkLeg/CircuitBreaker --skill cb-release -a claude-code`. Or copy the skill folder (.claude/skills/cb-release in BlkLeg/CircuitBreaker) into .claude/skills/cb-release in your project. Claude Code loads it when a task matches its description.

How do I install Cb Release in Codex?

Run `npx skills add BlkLeg/CircuitBreaker --skill cb-release -a codex`. Or copy the skill folder (.claude/skills/cb-release in BlkLeg/CircuitBreaker) into .agents/skills/cb-release in your project. Codex loads it when a task matches its description.

Can I use Cb Release in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add BlkLeg/CircuitBreaker --skill cb-release -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cb-release, .gemini/skills/cb-release, .github/skills/cb-release and .opencode/skills/cb-release in your project.

What does Cb Release need to run?

Going by SKILL.md and its folder, Cb Release needs the command-line tools its instructions call (make, git, gh and npx) and credentials named GITHUB_TOKEN. Our summary lists: Node.js; A credential in GITHUB_TOKEN.

Does Cb Release access the network?

SKILL.md contains no URLs. Its commands use git, gh and npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Cb Release safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Cb Release use?

Cb Release is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Cb Release use?

About 1.8k tokens (SKILL.md is roughly 7.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Cb Release?

Skills that share tags, products or a category with Cb Release: Cutting A Release (TriliumNext/Trilium, 38k stars), Mole CLI Release Flow (tw93/Mole, 70k stars), Draft Release Notes (jamiepine/voicebox, 57k stars) and Mole Release Notes Publisher (tw93/Mole, 70k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Cb Release?

BlkLeg (a GitHub user) maintains it in BlkLeg/CircuitBreaker, which has 201 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 5, 2026.

Source: BlkLeg/CircuitBreaker on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Cb Release

Install Cb Release

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Circuit Breaker — Releasing

The flow

Rules that each cost a failed release to learn

Diagnosing a red Release run

What a release does NOT prove

Touching release.yml

Files

Compare with similar skills

Similar skills

Cutting A Release

Mole CLI Release Flow

Draft Release Notes

Mole Release Notes Publisher

Release Bump

Cut Release

More from BlkLeg/CircuitBreaker

Cb Build Test

Cb Code Quality

Cb Realtime API

Cb Security Hardening

Cb Automation

Questions about Cb Release

Install Cb Release

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Circuit Breaker — Releasing

The flow

Rules that each cost a failed release to learn

Diagnosing a red Release run

What a release does NOT prove

Touching release.yml

Files

Compare with similar skills

Similar skills

More from BlkLeg/CircuitBreaker

Related

Questions about Cb Release