What is release-readiness?

A release checklist for preparing and publishing a version of the gencc-link project. It covers tests, documentation, version numbers, Docker settings, data checks, tagging, and the release workflow.

Use it before creating a gencc-link release to run local and coverage checks, inspect pending changes, update release files, validate the Docker build, check generated data, and monitor the release process.

It reduces the chance of publishing a release with failing checks, missing change notes, mismatched version numbers, invalid Docker settings, or bad data.

How berntpopp/gencc-link configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to berntpopp/gencc-link. 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/berntpopp/gencc-link/main/.claude/skills/release-readiness/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/berntpopp/gencc-link

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/skills/berntpopp/gencc-link/release-readiness/github.svg)](https://agentmods.dev/skills/berntpopp/gencc-link/release-readiness)

Your own site

<a href="https://agentmods.dev/skills/berntpopp/gencc-link/release-readiness"><img src="https://agentmods.dev/badge/skills/berntpopp/gencc-link/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/berntpopp/gencc-link/release-readiness"><img src="https://agentmods.dev/badge/skills/berntpopp/gencc-link/release-readiness.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 46 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 499 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 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.00046	$0.00499
Opus 5	$0.00023	$0.00249
Sonnet 5	$0.00009	$0.00100
Haiku 4.5	$0.00005	$0.00050

Measured 8d ago against content hash 9064770282f4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

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 8d 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/skills/release-readiness/SKILL.md · 53 lines

What it actually says

Release readiness

Pre-flight checklist

Confirm main is green: the latest CI run (ci.yml) succeeded.
Verify there are no outstanding Dependabot PRs that should land first.
Confirm CHANGELOG.md has an [Unreleased] (or current) section listing all user-visible changes since the last tag.

Run the gate locally and confirm it passes:

make ci-local
make test-cov     # coverage gate is 85%

Validate the Docker config and image build the release workflow will run:

docker compose -f docker/docker-compose.yml -f docker/docker-compose.prod.yml config
docker build -f docker/Dockerfile -t gencc-link:release .

Sanity-check the data path: make data builds a fresh database and make data-info reports sensible provenance and counts.

Bump

Open pyproject.toml and bump version (semver: MAJOR for breaking, MINOR for features, PATCH for fixes). Keep gencc_link/__init__.py __version__ and the user_agent default in config.py in sync if they reference it.
In CHANGELOG.md, rename the [Unreleased] heading to [X.Y.Z] - YYYY-MM-DD and add a fresh empty [Unreleased] section above it. Update the link references at the bottom.
Commit: chore(release): bump to X.Y.Z.

Tag and push

git tag vX.Y.Z
git push origin main vX.Y.Z

Watch

release.yml runs on v* tag pushes. It installs deps, runs make ci-local, validates the production Compose config, and builds the release Docker image.

Roll forward

If release.yml fails, fix on main, bump to vX.Y.(Z+1), and retag. Do not move or delete a published tag.

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.

8d ago First seen · 53 lines · 46 tokens per session scan A 9064770282f4

Subscribe to this mod's changes

release-readiness is a skill published in the GitHub repository berntpopp/gencc-link (0 stars, last pushed 4d ago), licensed MIT. It adds 46 tokens to every session and 499 once invoked, about $0.0002 per session on Opus 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-31.

CI and CD DevOps and cloud Git and workflow Releases bioinformatics clinical-genetics gencc gene-disease mcp model-context-protocol

release-and-publish

Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for .mcpb bundles, GHCR). Runs the final verification gate, pushes commits and tags, then publishes to each applicable destination. Assumes git wrapup (version bumps, changelog, commit, annotated tag) is already…

cyanheads/docgen-mcp-server · 112 tokens

git-wrapup

Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts) and an annotated tag. Verify, commit, tag. Stops at "committed and tagged locally" — no push, no publish. The release-and-publish skill picks up from here. Distilled…

cyanheads/uniprot-mcp-server · 82 tokens

gencc-link: Skill for Claude Code

Borrowing it

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

Release readiness

Pre-flight checklist

Bump

Tag and push

Watch

Roll forward

What this file has done since we first saw it

Other skills, from other repositories

release-and-publish

git-wrapup

release-and-publish

github-release-management

agent-github-modes

releasepr