What is release-check?

A pre-release checklist for GitCortex. It checks the branch, continuous-integration result, version references, changelog, security audit, and selected Rust library-code patterns.

Run it before preparing a GitCortex release. It checks repository cleanliness, CI, matching version numbers, release notes, dependency advisories, and unwanted unwrap or expect calls.

It finds release problems before a version is changed or a tag is created. It reports each item as passed or failed without changing the version or creating a tag.

release-check — Command by bharath03-a

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.

agentmods

npx agentmods add commands/bharath03-a/gitcortex/release-check

Clone the repo

git clone --depth 1 https://github.com/bharath03-a/GitCortex

Made for: Claude Code.

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 489 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

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	$0.00000	$0.00489
Opus 5	$0.00000	$0.00244
Sonnet 5	$0.00000	$0.00098
Haiku 4.5	$0.00000	$0.00049

Measured 2d ago against content hash b3445abc946b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

release-check 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 2d 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/dev/release-check.md · 41 lines

What it actually says

Pre-release gate for GitCortex. Run before bumping version. Reports a checklist with PASS/FAIL per item — do not bump or tag.

Checks:

Branch state — on main, clean tree, in sync with origin. git status --porcelain empty, git rev-list main..origin/main --count == 0.
CI green on HEAD — gh run list --branch main --limit 1 --json conclusion shows success.
Version consistency — every place that names a version agrees.
- cargo metadata --format-version 1 | jq '.workspace_metadata, .packages[].version'
- git grep -nE '"version":\s*"[0-9]' across package.json files
- git grep -nE '^version\s*=\s*"[0-9]' across pyproject.toml files
- README install snippets Report any mismatch with file:line.
CHANGELOG ready — CHANGELOG.md has an entry for the version about to ship (i.e. an unreleased section with content, not empty).
Audit clean — cargo audit exits 0, or every advisory is in audit.toml ignore list with a justification.
No unwrap regressions in library code — git grep -nE '\.(unwrap|expect)\(' -- 'crates/gitcortex-core/**/*.rs' 'crates/gitcortex-indexer/**/*.rs' 'crates/gitcortex-store/**/*.rs' should match only known/approved instances (compare against last release's count).
All tests pass — cargo nextest run --workspace.
MCP smoke test — gcx --version works, gcx serve --help lists expected tools.

Output format:

| # | Check                  | Status | Notes              |
| 1 | Branch state           | PASS   |                    |
| 2 | CI green               | FAIL   | last run errored   |
...

End with: READY TO RELEASE or BLOCKED ON: <list>.

If READY, suggest the next command (/release-gcx workflow via the skill, or manual bump).

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.

2d ago First seen · 41 lines · 0 tokens per session scan A b3445abc946b

Subscribe to this mod's changes

release-check is a command published in the GitHub repository bharath03-a/GitCortex (7 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 489 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-31.

DevOps and cloud Git and workflow Security

release-check

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other commands, from other repositories

checklist

clarify

specify

analyze

converge

implement