Borrowing it
Nothing to install: this file belongs to sachinshelke/codevira. 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/sachinshelke/codevira/main/.claude/skills/release-readiness/SKILL.mdgit clone --depth 1 https://github.com/sachinshelke/codeviraWrote 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/skills/sachinshelke/codevira/release-readiness)<a href="https://agentmods.dev/skills/sachinshelke/codevira/release-readiness"><img src="https://agentmods.dev/badge/skills/sachinshelke/codevira/release-readiness/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/skills/sachinshelke/codevira/release-readiness"><img src="https://agentmods.dev/badge/skills/sachinshelke/codevira/release-readiness.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.00096 | $0.02095 |
| Opus 5.5 | $0.00038 | $0.00838 |
| Sonnet 5.5 | $0.00019 | $0.00419 |
| Haiku 4.5 | $0.00010 | $0.00210 |
Grade A, and why
release-readiness 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.
How it starts
The opening of the file, as written. The whole thing — 230 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release readiness — the bypass-proof release gauntlet
v2.0.0 shipped to PyPI with 23 silent-failure bugs because nothing forced gauntlet-pass evidence before publish. This skill makes the gauntlet mandatory at the CONVERSATION layer (skills); the Makefile
- hook + CI enforce it at the TOOL layer. Both must agree before any release proceeds.
When this skill triggers
Trigger phrases:
- "ready to release"
- "let's ship"
- "publish to PyPI"
- "promote to production"
- "release X.Y.Z"
- "cut a release"
- "tag the version"
- "ship it"
- Any mention of
twine upload,gh release create --draft=false,pipx publish, etc.
When this skill triggers, you MUST walk the 5-gate gauntlet below before producing any actual release command.
The 5 gates
Defined in codevira.discipline.yaml::release_gates. Each must pass.
G1 — Unit tests
make test-unit
# OR: pytest tests/ -q --ignore=tests/e2e
Pass criterion: exit code 0, no test failures or unexpected skips.
G2 — First-contact e2e
make test-e2e
# OR: pytest tests/e2e/test_first_contact.py -v
Pass criterion: all 4 fixtures pass (docs_only, code_only_python, polyglot, monorepo). This is the gate that catches bugs A–O. If G2 shows failures, those failures ARE the v2.1 work list — don't release until they're fixed.
G3 — Real-IDE smoke
scripts/check_real_ide_smoke.sh
Pass criterion: codevira appears connected in Claude Code AND Claude
Desktop AND at least one other IDE. tools/list returns in <1s.
Today's state: the script is real and G3 has recorded true since
3.1.0. It was a stub before that, recording "skipped" — and this file
used to say that was "tolerable for v2.0.x but BLOCKING for v2.1".
It never became blocking. Six releases shipped with G3 unverified,
because a sentence in a skill is not an enforcement point.
It is enforced now: pre-release-block.sh refuses any gate that is not
true, with one stated exception (G4 may be "warn"). "skipped"
blocks.
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.
- 1mo ago Changed · +20 lines 1c0d17a99b9e
- 1mo ago First seen · 210 lines · 96 tokens per session scan A 84296714de63
release-readiness is a skill published in the GitHub repository sachinshelke/codevira (12 stars, last pushed 1mo ago), licensed MIT. It adds 96 tokens to every session and 2,095 once invoked, about $0.0004 per session on Opus 5.5. 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.
Other skills, from other repositories
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, splitting uncommitted work in a messy working tree into clean atomic commits, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple…
production-deployment
Zero-downtime deployments with pre-flight checks, staged rollouts, and rollback plans. Never ship to production without a verified rollback strategy.
shipping-and-launch
A production-release checklist and planning guide for putting software in front of real users. It covers testing, security, monitoring, staged rollout, and rollback, which means returning to the previous working version.
ci-cd-pipelines
Provides CI/CD pipeline structure, a GitHub Actions CI template, deployment gates, and an optimization checklist; use when designing GitHub Actions workflows, optimizing pipeline speed, or implementing deployment gates.
to-release
Prepare a library release on its PR (version, changelog, draft GitHub release) for review, then tag and publish it after you merge.
shipping-and-launch
Prepares production launches. Use when preparing to deploy to production. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.