Agent skill

ClawRouter Release Checklist

Walks the agent through every ClawRouter release step in order, from the version bump and changelog entry to build, tests, npm publish, git tag and GitHub release.

MITAuto-check passedDevelopment

Install ClawRouter Release Checklist

skills CLI

$ npx skills add BlockRunAI/ClawRouter --skill release -a claude-code

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

GitHub CLI

$ gh skill install BlockRunAI/ClawRouter 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/BlockRunAI/ClawRouter.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/release .claude/skills/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 "release" agent skill from https://github.com/BlockRunAI/ClawRouter/tree/main/skills/release into .claude/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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/BlockRunAI/ClawRouter/tree/main/skills/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 BlockRunAI/ClawRouter --skill release -a codex

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

GitHub CLI

$ gh skill install BlockRunAI/ClawRouter 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/BlockRunAI/ClawRouter.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/release .agents/skills/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 "release" agent skill from https://github.com/BlockRunAI/ClawRouter/tree/main/skills/release into .agents/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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 BlockRunAI/ClawRouter --skill release -a cursor

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

GitHub CLI

$ gh skill install BlockRunAI/ClawRouter 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/BlockRunAI/ClawRouter.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/release .cursor/skills/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 "release" agent skill from https://github.com/BlockRunAI/ClawRouter/tree/main/skills/release into .cursor/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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/BlockRunAI/ClawRouter.git --path skills/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 BlockRunAI/ClawRouter --skill release -a gemini-cli

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

GitHub CLI

$ gh skill install BlockRunAI/ClawRouter 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/BlockRunAI/ClawRouter.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/release .gemini/skills/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 "release" agent skill from https://github.com/BlockRunAI/ClawRouter/tree/main/skills/release into .gemini/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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 BlockRunAI/ClawRouter 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 BlockRunAI/ClawRouter --skill release -a github-copilot

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

Manual copy

$ git clone --depth 1 https://github.com/BlockRunAI/ClawRouter.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/release .github/skills/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 "release" agent skill from https://github.com/BlockRunAI/ClawRouter/tree/main/skills/release into .github/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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 BlockRunAI/ClawRouter --skill 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 BlockRunAI/ClawRouter 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/BlockRunAI/ClawRouter.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/release .opencode/skills/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 "release" agent skill from https://github.com/BlockRunAI/ClawRouter/tree/main/skills/release into .opencode/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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: release
GitHub stars: 6.6k
Token cost: ~1.4k tokens
SKILL.md length: 446 words
Files: 1
Skills in repo: 7
Repo updated: Oct 5, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Walks the agent through every ClawRouter release step in order, from the version bump and changelog entry to build, tests, npm publish, git tag and GitHub release.

Works in 12 steps: Confirm the New Version → Update package.json Version → Write CHANGELOG Entry → …
Cutting a new ClawRouter version for release
SKILL.md covers Step 1: Confirm the New Version, Step 2: Update package.json…, Step 3: Write CHANGELOG Entry and Step 4: Confirm No Manual…, plus 9 more sections
Calls npm, git and gh; reaches registry.npmjs.org

What it does

This skill is a mandatory, ordered checklist for releasing the ClawRouter package, and the agent is told to run every step without skipping any. It begins by reading the current version from package.json, asking which version you are releasing and checking that it follows semver and is higher than the current one, then bumps the version field.

Next it adds a section at the top of CHANGELOG.md with one bullet per logical change, covering everything since the previous release and dated in a style like Mar 8, 2026. A short step explains that the BlockRun server now fetches the latest version from the npm registry, so no manual version constant needs editing. The build runs next, then tests, typecheck and lint, which must all pass before the commit. The remaining steps are npm publish, a git tag and a GitHub release.

When your agent uses it

Cutting a new ClawRouter version for release
Writing the CHANGELOG entry for an upcoming release
Publishing the package to npm and tagging the release in git

Example prompts

“Release the next ClawRouter version and make sure the changelog covers every change since the last one.”
“Bump the package version, run the build, tests, typecheck and lint, then publish to npm.”
“We are shipping a ClawRouter patch today, so go through the full release checklist.”

Requirements

A ClawRouter checkout with npm build, test, typecheck and lint scripts
Permission to publish the package to npm and create GitHub releases

Workflow steps

12 steps, taken from the step headings in SKILL.md.

Confirm the New Version
Update package.json Version
Write CHANGELOG Entry
Confirm No Manual Server Sync Required
Build
Run Tests
Commit Everything
Push to GitHub
Create Git Tag
Create GitHub Release
Publish to npm
Final Verification

What it can do on your machine

Read from SKILL.md and the folder at commit b758e03. 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:
- npm
- git
- gh
- node
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
- registry.npmjs.org
Also links to:
- npmjs.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

ClawRouter Release Checklist loads about 1.4k tokens when it runs. Until then it costs about 46 tokens; SKILL.md has 446 words of instructions outside code blocks.

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

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 BlockRunAI/ClawRouter at commit b758e03, republished under its MIT licence (© BlockRunAI). 446 words, ~1,383 tokens.

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

name: release
description: Use this skill for EVERY ClawRouter release. Enforces the full checklist — version sync, CHANGELOG, build, tests, npm publish, git tag, GitHub release. No step can be skipped.
triggers: release clawrouter, ship clawrouter, publish clawrouter, version bump clawrouter, tag clawrouter release, npm publish clawrouter, clawrouter release

ClawRouter Release Checklist

This skill is mandatory for every release. Execute every step in order. Do not skip.

Step 1: Confirm the New Version

Read the current version:

bash

cat package.json | grep '"version"'

Ask: "What version are we releasing?" Confirm it follows semver and is higher than current.

Step 2: Update `package.json` Version

Edit package.json — bump "version" to the new version.

Step 3: Write CHANGELOG Entry

Open CHANGELOG.md. Add a new section at the top (after the header) in this format:

markdown

## v{VERSION} — {DATE}

- **Feature/Fix name** — description
- **Feature/Fix name** — description

Rules:

Date format: Mar 8, 2026
One bullet per logical change
Every bullet must be present — no "see git log"
Include all changes since the previous release

Step 4: Confirm No Manual Server Sync Required

No file edit needed here. Earlier releases (pre-v0.12.x) required manually updating a CURRENT_CLAWROUTER_VERSION constant in blockrun's src/app/api/v1/chat/completions/route.ts. That constant has been replaced: the server now fetch-es https://registry.npmjs.org/@blockrun/clawrouter/latest at process startup and uses the returned version to drive the update_available hint embedded in 429 responses to outdated clients.

typescript

// blockrun/src/app/api/v1/chat/completions/route.ts
let latestClawRouterVersion: string | null = process.env.CLAWROUTER_CURRENT_VERSION || null;
fetch("https://registry.npmjs.org/@blockrun/clawrouter/latest", {
  signal: AbortSignal.timeout(5000),
})
  .then((r) => r.json())
  .then((data) => {
    if (data.version) latestClawRouterVersion = data.version;
  })
  .catch(() => {
    /* keep env var fallback */
  });

Implications:

The npm publish in Step 11 IS the entire "sync blockrun" action. After that step lands, the next blockrun server restart will fetch and surface the new version. No manual constant edit. No separate PR in the blockrun repo.
CLAWROUTER_CURRENT_VERSION env var is the cold-start fallback (used only when the registry fetch fails). It exists for resilience, not as the primary mechanism — don't touch it on every release.
Verification of the user-facing update nudge happens in Step 12 via npm view @blockrun/clawrouter version (the same registry endpoint blockrun's server hits).

Skip to Step 5.

Step 5: Build

bash

npm run build

Fix any TypeScript or build errors before proceeding.

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

Step 6: Run Tests

bash

npm test
npm run typecheck
npm run lint

All must pass. Fix failures before proceeding.

Step 7: Commit Everything

Stage and commit:

bash

git add package.json CHANGELOG.md
git commit -m "chore: bump version to {VERSION}"

No companion commit in the blockrun repo is needed — the server picks up new versions automatically via the npm registry fetch documented in Step 4.

Step 8: Push to GitHub

bash

git push origin main

Step 9: Create Git Tag

bash

git tag v{VERSION}
git push origin v{VERSION}

Step 10: Create GitHub Release

bash

gh release create v{VERSION} \
  --title "v{VERSION}" \
  --notes "$(sed -n '/^## v{VERSION}/,/^## v[0-9]/p' CHANGELOG.md | head -n -1)"

Verify the release on GitHub: https://github.com/BlockRunAI/ClawRouter/releases

The release notes must match the CHANGELOG entry exactly.

Step 11: Publish to npm

bash

npm publish --access public

Verify: https://npmjs.com/package/@blockrun/clawrouter

Expected output: + @blockrun/clawrouter@{VERSION}

Step 12: Final Verification

Run this checklist to confirm everything is in sync:

bash

# 1. package.json version
node -p 'require("./package.json").version'

# 2. CHANGELOG has the entry
head -10 CHANGELOG.md

# 3. npm package is live (this is also what blockrun's server fetches —
#    matching version here means the user-facing update nudge will fire correctly)
npm view @blockrun/clawrouter version

# 4. GitHub tag exists
git tag --list 'v{VERSION}'

# 5. GitHub release exists
gh release view v{VERSION}

All 5 must match the new version. If any mismatch, fix before declaring the release done.

Common Mistakes (Never Repeat These)

Mistake	Prevention
Hand-editing `CURRENT_CLAWROUTER_VERSION` (no longer exists)	Step 4 — server now auto-fetches
CHANGELOG entry missing or incomplete	Step 3 — write it before building
npm publish before tests pass	Steps 5-6 must precede Step 11
GitHub release notes empty	Step 10 — extract from CHANGELOG
Git tag not pushed	Step 9 — push tag separately
docs not reflecting new features	Update docs in same PR as the feature

Files

Just SKILL.md in skills/release of BlockRunAI/ClawRouter.

Open the folder on GitHubat commit b758e03

Compare with similar skills

ClawRouter Release Checklist 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.

ClawRouter Release Checklist compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
ClawRouter Release Checklist this skillBlockRunAI/ClawRouter	6.6k	—	~1.4k	Automated safety check: Pass	MIT	3 days ago
Hunk Release Workflowmodem-dev/hunk	9.5k	—	~3.8k	Automated safety check: Pass	MIT	yesterday
ZCF Release AutomationUfoMiao/zcf	6.1k	—	~3.4k	Automated safety check: Pass	MIT	1 mo ago
Releasedcb/homeassistant-claude-kit	123	—	~3.1k	Automated safety check: Pass	MIT	6 days ago
ClickUp CLI Release Processkrodak/clickup-cli	121	—	~906	Automated safety check: Warn	MIT	2 days ago
Worktrunk Release Workflowmax-sixty/worktrunk	9k	—	~6.9k	Automated safety check: Pass	Custom licence	today

Similar skills

Hunk Release Workflow
modem-dev/hunk
Maintainer workflow for preparing, publishing, verifying and curating Hunk releases, with confirmation gates before tags, publishes and public edits.
9.5k GitHub stars~3.8k tokensUpdated yesterday
DevelopmentAuto-check passed
ZCF Release Automation
UfoMiao/zcf
Automates a version release with changesets: analyzes code changes, writes a bilingual CHANGELOG, bumps the version and commits through a release branch and pull request.
6.1k GitHub stars~3.4k tokensUpdated 1 mo ago
DevelopmentAuto-check passed
Release
dcb/homeassistant-claude-kit
Cut a new homeassistant-claude-kit version. An agent skill from dcb/homeassistant-claude-kit.
123 GitHub stars~3.1k tokensUpdated 6 days ago
DevelopmentAuto-check passed
ClickUp CLI Release Process
krodak/clickup-cli
Walks through releasing a new version of clickup-cli: pre-release checks, version bump, tagging, CI watch, release notes and the Homebrew update.
121 GitHub stars~906 tokensUpdated 2 days ago
DevOps & CloudAuto-check: warnings
Worktrunk Release Workflow
max-sixty/worktrunk
Walks a maintainer through cutting a Worktrunk release: sync the release branch, pass two test gates, review the changes, then publish.
9k GitHub stars~6.9k tokensUpdated today
DevelopmentAuto-check passed
Remotion Bits Release
av/remotion-bits
Runs the full release of the remotion-bits package: version bump, changelog, registry build, release commit, GitHub release, docs deploy and npm publish.
487 GitHub stars~1.2k tokensUpdated 22 days ago
DevelopmentAuto-check passed

Questions about ClawRouter Release Checklist

What does ClawRouter Release Checklist do?

Walks the agent through every ClawRouter release step in order, from the version bump and changelog entry to build, tests, npm publish, git tag and GitHub release. This skill is a mandatory, ordered checklist for releasing the ClawRouter package, and the agent is told to run every step without skipping any.json, asking which version you are releasing and checking that it follows semver and is higher than the current one, then bumps the version field.

When should I use ClawRouter Release Checklist?

ClawRouter Release Checklist fits situations like: cutting a new ClawRouter version for release; writing the CHANGELOG entry for an upcoming release; publishing the package to npm and tagging the release in git.

How do I install ClawRouter Release Checklist in Claude Code?

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

How do I install ClawRouter Release Checklist in Codex?

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

Can I use ClawRouter Release Checklist 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 BlockRunAI/ClawRouter --skill 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/release, .gemini/skills/release, .github/skills/release and .opencode/skills/release in your project.

What does ClawRouter Release Checklist need to run?

Going by SKILL.md and its folder, ClawRouter Release Checklist needs the command-line tools its instructions call (npm, git, gh and node). Our summary lists: A ClawRouter checkout with npm build, test, typecheck and lint scripts; Permission to publish the package to npm and create GitHub releases.

Does ClawRouter Release Checklist access the network?

SKILL.md names 2 domains. In commands or code: registry.npmjs.org; the agent is likely to contact it when it follows the instructions. As links in the text: npmjs.com. This is read from the text; nothing was executed.

Is ClawRouter Release Checklist 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 ClawRouter Release Checklist use?

ClawRouter Release Checklist 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 ClawRouter Release Checklist use?

About 1.4k tokens (SKILL.md is roughly 5.5k 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 ClawRouter Release Checklist?

Skills that share tags, products or a category with ClawRouter Release Checklist: Hunk Release Workflow (modem-dev/hunk, 9.5k stars), ZCF Release Automation (UfoMiao/zcf, 6.1k stars), Release (dcb/homeassistant-claude-kit, 123 stars) and ClickUp CLI Release Process (krodak/clickup-cli, 121 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains ClawRouter Release Checklist?

BlockRunAI (a GitHub organization) maintains it in BlockRunAI/ClawRouter, which has 6,617 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 5, 2026.

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

Install ClawRouter Release Checklist

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

ClawRouter Release Checklist

Step 1: Confirm the New Version

Step 2: Update package.json Version

Step 3: Write CHANGELOG Entry

Step 4: Confirm No Manual Server Sync Required

Step 5: Build

Step 6: Run Tests

Step 7: Commit Everything

Step 8: Push to GitHub

Step 9: Create Git Tag

Step 10: Create GitHub Release

Step 11: Publish to npm

Step 12: Final Verification

Common Mistakes (Never Repeat These)

Files

Compare with similar skills

Similar skills

More from BlockRunAI/ClawRouter

Related

Questions about ClawRouter Release Checklist

Step 2: Update `package.json` Version