A project release checklist that covers the working tree, version naming, changelog, tests, and release preparation.

Use it to prepare a project release, determine the next release name and version, check required validation, and report anything that must be fixed first.

It makes release work repeatable and requires confirmation before commits, pushes, pull requests, or tags are created.

How nanotaboada/python-samples-fastapi-restful configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to nanotaboada/python-samples-fastapi-restful. 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/nanotaboada/python-samples-fastapi-restful/master/.claude/commands/pre-release.md

Clone the repo

git clone --depth 1 https://github.com/nanotaboada/python-samples-fastapi-restful

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/commands/nanotaboada/python-samples-fastapi-restful/pre-release/github.svg)](https://agentmods.dev/commands/nanotaboada/python-samples-fastapi-restful/pre-release)

Your own site

<a href="https://agentmods.dev/commands/nanotaboada/python-samples-fastapi-restful/pre-release"><img src="https://agentmods.dev/badge/commands/nanotaboada/python-samples-fastapi-restful/pre-release/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/commands/nanotaboada/python-samples-fastapi-restful/pre-release"><img src="https://agentmods.dev/badge/commands/nanotaboada/python-samples-fastapi-restful/pre-release.svg" alt="Reviewed on agentmods" width="80" 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 780 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.00000	$0.00780
Opus 5.5	$0.00000	$0.00312
Sonnet 5.5	$0.00000	$0.00156
Haiku 4.5	$0.00000	$0.00078

Measured 2mo ago against content hash 6c3bc13cfd91, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

pre-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 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.

.claude/commands/pre-release.md · 89 lines

How it starts

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

Pre-release checklist

Run the pre-release checklist for this project.

Working style: propose before acting at every step — do not commit, push, open PRs, or create tags until I explicitly confirm.

Phase 1 — Determine next release

Verify working tree: Confirm we are on master with a clean working tree. If behind the remote, propose git pull and wait for confirmation before pulling.

Detect current release and propose next: Read CHANGELOG.md for the coach naming convention (A–Z table) and the most recent release heading. Run git tag --sort=-v:refname to confirm the latest tag. Then:

Next codename: next letter in the A–Z sequence after the current one. Use lowercase with no spaces for the tag (e.g. eriksson); Title Case for the CHANGELOG heading (e.g. Eriksson). If no tags exist yet, start at A (first coach in the table). If letters were skipped, pick the next after the highest existing codename — do not backfill gaps. If the last codename is Z (Zeman), the list is finite — stop and flag that the naming convention needs to be revisited.

Version bump — infer from [Unreleased]:

Condition	Bump
Any entry marked BREAKING (case-insensitive), `BREAKING CHANGE:` token in a commit footer, or `!` suffix after type/scope (e.g. `feat!:`)	MAJOR
Entries under Added	MINOR
Only Changed / Fixed / Removed	PATCH

If [Unreleased] has no entries, stop and warn — there is nothing to release.

Present a summary before proceeding:

Current:  v2.1.0-delbosque
Proposed: v2.2.0-eriksson  (MINOR — new features in Added)
Branch:   release/v2.2.0-eriksson
Tag:      v2.2.0-eriksson

Phase 2 — Prepare release branch

Create release branch: release/vX.Y.Z-{codename}.
Update CHANGELOG.md: Move all content under [Unreleased] into a new versioned heading [X.Y.Z - Codename] - {today's date}. Replace [Unreleased] with a fresh empty template:

Read the full file on GitHub · 89 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.

2mo ago First seen · 89 lines · 0 tokens per session scan A 6c3bc13cfd91

Subscribe to this mod's changes

pre-release is a command published in the GitHub repository nanotaboada/python-samples-fastapi-restful (141 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 780 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 Python fastapi proof-of-concept pydantic rest-api sqlalchemy

pre-release next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
pre-releasenanotaboada/python-samples-fastapi-restful	Command	141	4d ago	MIT	A	0	Claude Code
reviewvstorm-co/full-stack-ai-agent-template	Command	2.0k	7d ago	MIT	A	6	Claude Code
deployNickRomanek/clawbridge	Command	23	19d ago	Apache-2.0	A	0	Claude Code
speckit.taskstoissuesSpillwaveSolutions/agent-brain	Command	119	1mo ago	MIT	A	21	Claude Code
addsheep-programmer/AIForge	Command	3	4mo ago	none	A	9	Claude Code
checklistgithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	148k	yesterday	MIT	A	27	Claude Code

python-samples-fastapi-restful: Command for Claude Code