What is sonicjs-release-engineer?

A release-management agent for SonicJS npm packages, which are JavaScript packages published through npm. It handles dependency updates, versioning, publishing, and release tags according to SonicJS's beta-release rules.

Use it for SonicJS dependency updates, npm package releases, beta version increments, publishing, and keeping the beta and latest tags aligned.

It reduces mistakes when updating packages and publishing beta releases, especially around version numbers and npm tags. The input does not describe its full command set.

How SonicJs-Org/sonicjs configures Claude Code

About the project

SonicJS is a TypeScript-first headless content-management system that exposes content through REST APIs and an administrative interface, running on Cloudflare Workers or other SQLite-compatible environments. It is for developers building applications that manage and publish structured content, with storage through technologies such as D1 and R2. Catalogue add-ons help coding agents create and work with SonicJS projects and content.

SonicJs-Org/sonicjs · 1,788 stars · on GitHub · sonicjs.com

Reuse

Borrowing it

Nothing to install: this file belongs to SonicJs-Org/sonicjs. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/SonicJs-Org/sonicjs/main/.claude/commands/sonicjs-release-engineer.md

Clone the repo

git clone --depth 1 https://github.com/SonicJs-Org/sonicjs

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/sonicjs-org/sonicjs/sonicjs-release-engineer/github.svg)](https://agentmods.dev/commands/sonicjs-org/sonicjs/sonicjs-release-engineer)

Your own site

<a href="https://agentmods.dev/commands/sonicjs-org/sonicjs/sonicjs-release-engineer"><img src="https://agentmods.dev/badge/commands/sonicjs-org/sonicjs/sonicjs-release-engineer/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/sonicjs-org/sonicjs/sonicjs-release-engineer"><img src="https://agentmods.dev/badge/commands/sonicjs-org/sonicjs/sonicjs-release-engineer.svg" alt="Reviewed on agentmods" width="80" 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 3,912 The whole file, excluding the scripts and references it only reads on demand.

Security scan C 1 finding. 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.03912
Opus 5.5	$0.00000	$0.01565
Sonnet 5.5	$0.00000	$0.00782
Haiku 4.5	$0.00000	$0.00391

Measured 2mo ago against content hash 0ed91613f5a0, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade C, and why

sonicjs-release-engineer scanned grade C with 1 finding 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 2mo 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

rm -rf test-app

.claude/commands/sonicjs-release-engineer.md · 470 lines

How it starts

The opening of the file, as written. The whole thing — 470 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Release Engineer Agent

Critical Rules (NEVER violate without explicit instruction)

ALL releases use npm run version:beta (3.x.x-beta.N → 3.x.x-beta.N+1) until the user explicitly says "we are out of beta" or "release stable". NEVER use version:patch, version:minor, or version:major for routine releases — those drop the pre-release suffix and publish a stable version.
NEVER add --tag beta (or alpha/rc) when publishing — all publishes go to latest dist-tag regardless of the version string containing -beta.N.
The beta dist-tag MUST always point to the same version as latest. After any publish, run: npm dist-tag add @sonicjs-cms/core@<VERSION> beta && npm dist-tag add create-sonicjs@<VERSION> beta
Versions may contain -beta.N in the version string — that is fine and expected. The dist-tag (latest) is what matters for npm install behavior.

You are a specialized agent that manages npm package releases and dependency updates for SonicJS. Your primary responsibilities are:

Updating npm dependencies - Keep dependencies current and secure
Publishing packages to npm - Release new versions of @sonicjs-cms/core and create-sonicjs
Updating feature documentation - Ensure website docs reflect product changes included in each release

Background

SonicJS is a monorepo with two published npm packages:

@sonicjs-cms/core - The core CMS framework
create-sonicjs - The CLI scaffolding tool

Version synchronization is automatic via scripts/sync-versions.js.

Workflow 1: Update Dependencies

When asked to update dependencies, follow these steps:

Step 1: Check for Outdated Packages

npm outdated

Step 2: Review Security Vulnerabilities

npm audit

Step 3: Update Dependencies

For safe updates (patch/minor within semver):

npm update

For updating to latest major versions (review breaking changes first):

npx npm-check-updates -u
npm install

Read the full file on GitHub · 470 lines

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.

2mo ago First seen · 470 lines · 0 tokens per session scan C 0ed91613f5a0

Subscribe to this mod's changes

sonicjs-release-engineer is a command published in the GitHub repository SonicJs-Org/sonicjs (1,788 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,912 tokens. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Git and workflow Releases api cloudflare-workers cms headless-cms javascript rest-api

sonicjs-release-engineer next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
sonicjs-release-engineerSonicJs-Org/sonicjs	Command	1.8k	yesterday	MIT	C	0	Claude Code
discover-changelogbuildinternet/releases	Command	13	yesterday	Apache-2.0	A	0	Claude Code
customer-changelog-checkheymegabyte/claude-skills	Command	22	1mo ago	none	A	0	Claude Code
rollbackheymegabyte/claude-skills	Command	22	1mo ago	none	A	25	Claude Code
landgmickel/flow-next	Command	717	yesterday	MIT	A	13	Claude Code
qualityDesko77/claude-code-skills-1c	Command	90	yesterday	MIT	A	18	Claude Code
release-notesOpenHands/extensions	Command	176	yesterday	MIT	A	44	Claude Code

sonicjs: Command for Claude Code