An interactive checklist for releasing a new version of llmwiki, a software project. It covers tests, builds, documentation, version numbers, and other release checks.

Running the llmwiki release process with the /release command, checking the project, updating its version and changelog, and completing the remaining release steps.

It reduces the chance of publishing a release with failing tests, build problems, missing updates, or known critical bugs.

release — Command for Claude Code by Pratiyush: An interactive checklist for releasing a new version of…

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/pratiyush/llm-wiki/release

Clone the repo

git clone --depth 1 https://github.com/Pratiyush/llm-wiki

Made for: Claude Code.

Or install llm-wiki, the plugin that ships this one along with the rest of its 6 skills, 18 commands.

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/commands/pratiyush/llm-wiki/release.svg)](https://agentmods.dev/commands/pratiyush/llm-wiki/release)

Your own site

<a href="https://agentmods.dev/commands/pratiyush/llm-wiki/release"><img src="https://agentmods.dev/badge/commands/pratiyush/llm-wiki/release.svg" alt="Measured on agentmods" height="20"></a>

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 920 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.00920
Opus 5	$0.00000	$0.00460
Sonnet 5	$0.00000	$0.00184
Haiku 4.5	$0.00000	$0.00092

Measured 4d ago against content hash 2b70a7378c09, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 4d 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/release.md · 94 lines

How it starts

The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Walk the llmwiki release process step by step.

Usage: /release # e.g. /release 0.9.0

This slash command loads docs/maintainers/RELEASE_PROCESS.md and walks through every step interactively. The rule is: don't skip a step even if it "should be" fine — skipping steps is how broken releases ship.

Workflow

Load the release process doc — docs/maintainers/RELEASE_PROCESS.md has the canonical checklist. Read it end to end before doing anything.
Run the pre-flight — confirm all of:
- Master is green (gh run list --branch master --limit 5)
- python3 -m pytest tests/ -q passes on a clean checkout
- python3 -m llmwiki build completes without new warnings
- Preview the built site and click through every nav item
- No open priority:critical bugs (gh issue list --label priority:critical --state open)
If any of these fail, stop and fix them first.
Bump the version — three files must agree:
- llmwiki/__init__.py → __version__ = "<NEW>"
- pyproject.toml → version = "<NEW>"
- README.md → version badge (Version-v<NEW>-7C3AED.svg) Run python3 -m llmwiki --version to confirm.
Update CHANGELOG — for every entry:
- Move from ## [Unreleased] into ## [<NEW>] — YYYY-MM-DD
- Group by ### Added / ### Changed / ### Fixed / ### Removed
- Add a one-line "Theme:" at the top of the new section
- Keep an empty ## [Unreleased] section above
Spot-check PR numbers — every #N in the new section should link to a real merged PR. Run gh pr list --state merged --limit 30 and cross-reference.

Commit and tag — use these exact commands:

git add llmwiki/__init__.py pyproject.toml README.md CHANGELOG.md
git commit -m "release(v<NEW>): bump version + CHANGELOG"
git tag v<NEW>
git push origin master v<NEW>

Do NOT force-push master. Do NOT amend the release commit after tagging.

Create the GitHub Release:
```
gh release create v<NEW> --title "v<NEW>" --notes-from-tag --prerelease
```
The --prerelease flag stays set for every 0.x.y until 1.0.0.
Verify the Pages deploy:
```
gh run list --workflow=pages.yml --limit=3
```
The new tag + the master push should both trigger the workflow. Watch both runs. Visit https://pratiyush.github.io/llm-wiki/ and confirm the new version badge is visible.
Announce (optional) — post to X / LinkedIn if it's a milestone release (v0.5, v0.9, v1.0, ...).
Append to log — one line to wiki/log.md:
```
## [YYYY-MM-DD] release | v<NEW>
```

Read the full file on GitHub · 94 lines

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.

4d ago First seen · 94 lines · 0 tokens per session scan A 2b70a7378c09

Subscribe to this mod's changes

release is a command published in the GitHub repository Pratiyush/llm-wiki (383 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 920 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-30.

Git and workflow Releases ai claude-code codex-cli cursor developer-tools karpathy

release

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Workflow

What this file has done since we first saw it

Other commands, from other repositories

sync-doctor

sync-validate

sync-list

/opsx-propose

note

/opsx-apply