A release command for publishing a new version of the skills-check project. It calculates a patch, minor, or major version change, checks the project, updates package versions, and pushes the release to Git.

Use it to prepare a release, run tests and builds, update all package.json files, create version tags, and push the commit and tags to GitHub.

It removes the need to remember the release order and the checks required before publishing. It also keeps version numbers and Git tags aligned across the project.

release — Command for Claude Code by voodootikigod

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo

git clone --depth 1 https://github.com/voodootikigod/skills-check

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/voodootikigod/skills-check/release.svg)](https://agentmods.dev/commands/voodootikigod/skills-check/release)

Your own site

<a href="https://agentmods.dev/commands/voodootikigod/skills-check/release"><img src="https://agentmods.dev/badge/commands/voodootikigod/skills-check/release.svg" alt="Measured on agentmods" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 404 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.00404
Opus 5	$0.00000	$0.00202
Sonnet 5	$0.00000	$0.00081
Haiku 4.5	$0.00000	$0.00040

Measured 8d ago against content hash 40e8b97b432c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

release scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/commands/release.md · 49 lines

What it actually says

Release a new version of skills-check.

Arguments

$ARGUMENTS: Version bump type — "patch", "minor", or "major". Defaults to "minor" if not specified.

Steps

Determine the new version. Read the current version from packages/cli/package.json. Apply the requested semver bump ($ARGUMENTS, default "minor") to compute the new version number.
Verify preconditions:
- Working tree is clean (git status --porcelain is empty)
- On the main branch
- Up to date with remote (git pull --dry-run shows no changes)
- All tests pass (npm test)
- Build succeeds (npm run build)
Bump version in ALL package.json files (must stay in lock step):
- package.json (root)
- packages/cli/package.json
- packages/schema/package.json
- packages/web/package.json
Commit the version bump:
```
chore: bump version to X.Y.Z
```
Create the version tag: vX.Y.Z

Push commit and tag:

git push origin main
git push origin vX.Y.Z

Update the floating major version tag (e.g., v1 for any 1.x.x release):
```
git tag -f vMAJOR
git push origin vMAJOR --force
```
This ensures users referencing voodootikigod/skills-check@v1 in GitHub Actions get the latest release.
Confirm completion. Print a summary of:
- Previous version → new version
- Tag created
- Floating tag updated
- Remind that publish.yml will handle npm publish automatically from the new tag

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

8d ago First seen · 49 lines · 0 tokens per session scan A 40e8b97b432c

Subscribe to this mod's changes

release is a command published in the GitHub repository voodootikigod/skills-check (13 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 404 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Git and workflow Releases agent agent-skills agentic-ai skills

release

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

Arguments

Steps

What this file has done since we first saw it

Other commands, from other repositories

OpenSpec: Archive

release

release-manager

release-swarm

CHANGELOG

dashboard-git-branches