coderag: Command for Claude Code

.claude/commands/release.md

release is a command for Claude Code from SylphxAI/coderag. It costs 9 tokens per session (547 once invoked), scanned A, a copy of release, MIT.

A release command for preparing, publishing, and monitoring a new software version. It checks tests, linting, builds, security, dependencies, documentation, version numbers, changelogs, CI/CD runs, and package publication.

In plain words
What is it for?
Use it to choose a version bump, update package files and changelogs, create release commits or tags, monitor automation, and verify that the package was published.
Why use it?
It helps reduce the chance of publishing a broken, undocumented, incorrectly versioned, or unavailable release.

Command for Claude Code

Written for Claude Code: installed under .claude/. Also seen: agent in frontmatter.

This is SylphxAI/coderag's own configuration. It tells Claude Code how to work on coderag itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything coderag configures →

Reuse

Borrowing it

Nothing to install: this file belongs to SylphxAI/coderag. 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/SylphxAI/coderag/main/.claude/commands/release.md
Clone the repo
git clone --depth 1 https://github.com/SylphxAI/coderag

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.

agentmods badge for release

README.md
[![agentmods](https://agentmods.dev/badge/commands/sylphxai/coderag/release/github.svg)](https://agentmods.dev/commands/sylphxai/coderag/release)
Your own site
<a href="https://agentmods.dev/commands/sylphxai/coderag/release"><img src="https://agentmods.dev/badge/commands/sylphxai/coderag/release/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.

agentmods 80×15 button for release

Your own site · 80×15
<a href="https://agentmods.dev/commands/sylphxai/coderag/release"><img src="https://agentmods.dev/badge/commands/sylphxai/coderag/release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 547 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 100% copy Near-identical to another mod 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00009 $0.00547
Opus 5.5 $0.00004 $0.00219
Sonnet 5.5 $0.00002 $0.00109
Haiku 4.5 $0.00001 $0.00055

Measured 1mo ago against content hash 7c90b2fa5bfd, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 1mo 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.

Origin

This is a copy

100% identical to release — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/commands/release.md · 105 lines

What it actually says

Release & Publish

Prepare, publish, and monitor package release.

Pre-Release Checks

Quality Gates:

  • All tests pass
  • No lint errors
  • Build successful
  • No security vulnerabilities
  • Dependencies up to date
  • CHANGELOG updated
  • README accurate
  • Breaking changes documented

Version Decision:

  • Breaking changes → major
  • New features → minor (default)
  • Bug fixes → patch

Release Process

For TypeScript/JavaScript Projects

  1. Create Changeset:

    bunx changeset
    
    • Select package
    • Choose version bump type
    • Write clear summary
  2. Version Bump:

    bunx changeset version
    
    • Updates package.json
    • Updates CHANGELOG.md
    • Consumes changeset
  3. Commit & Push:

    git add -A
    git commit -m "chore(release): <package>@<version>"
    git push
    
  4. Monitor CI:

    gh run list --workflow=release --limit 5
    gh run watch <run-id>
    
  5. Verify Publication:

    npm view <package>@<version>
    

For Other Projects

  1. Update version in manifest (package.json, setup.py, etc.)
  2. Update CHANGELOG
  3. Create git tag
  4. Push tag to trigger release
  5. Monitor CI/CD

Post-Release

  • Verify package published
  • Test installation: npm install <package>@latest
  • Create GitHub release with notes
  • Announce (if public package)
  • Close related issues/PRs

Troubleshooting

CI fails on install:

  • Update lockfile locally: bun install
  • Commit and push

Tests fail in CI:

  • Run tests locally: npm test
  • Fix issues, commit, push

Build fails:

  • Check build locally: npm run build
  • Fix errors, commit, push

Exit Criteria

  • Package published successfully
  • CI workflow completed
  • GitHub release created
  • Version verified on registry
  • Installation tested

Report: Version number, publish time, registry URL.

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.

  1. 1mo ago First seen · 105 lines · 9 tokens per session scan A 7c90b2fa5bfd

Subscribe to this mod's changes

release is a command published in the GitHub repository SylphxAI/coderag (12 stars, last pushed 1mo ago), licensed MIT. It adds 9 tokens to every session and 547 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to release, differing in 0 lines, and is treated as a copy.