Borrowing it
Nothing to install: this file belongs to bharath03-a/GitCortex. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/bharath03-a/GitCortex/main/.claude/commands/dev/release-check.mdgit clone --depth 1 https://github.com/bharath03-a/GitCortexWrote 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.
[](https://agentmods.dev/commands/bharath03-a/gitcortex/release-check)<a href="https://agentmods.dev/commands/bharath03-a/gitcortex/release-check"><img src="https://agentmods.dev/badge/commands/bharath03-a/gitcortex/release-check/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.
<a href="https://agentmods.dev/commands/bharath03-a/gitcortex/release-check"><img src="https://agentmods.dev/badge/commands/bharath03-a/gitcortex/release-check.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00489 |
| Opus 5.5 | $0.00000 | $0.00196 |
| Sonnet 5.5 | $0.00000 | $0.00098 |
| Haiku 4.5 | $0.00000 | $0.00049 |
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 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.
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.
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 --porcelainempty,git rev-list main..origin/main --count== 0. -
CI green on HEAD —
gh run list --branch main --limit 1 --json conclusionshowssuccess. -
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]'acrosspackage.jsonfilesgit grep -nE '^version\s*=\s*"[0-9]'acrosspyproject.tomlfiles- README install snippets Report any mismatch with file:line.
-
CHANGELOG ready —
CHANGELOG.mdhas an entry for the version about to ship (i.e. an unreleased section with content, not empty). -
Audit clean —
cargo auditexits 0, or every advisory is inaudit.tomlignore 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 --versionworks,gcx serve --helplists 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).
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 · 41 lines · 0 tokens per session scan A b3445abc946b
release-check is a command published in the GitHub repository bharath03-a/GitCortex (8 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.
Other commands, from other repositories
land
Resolve and squash merge one named, currently authorized pull request.
quality
A command for temporarily clearing a release quality gate or one named check, while recording the reason and expiry time. A quality gate is a required check that normally blocks completion or release.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
release-manager
Automated release coordination and deployment with ruv-swarm orchestration for seamless version management, testing, and deployment across multiple packages.
release-plan
A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.
create-pr
Push the current branch and open a pull request into main with a structured description derived from the branch's commits and the open issues it resolves.