What is cut-a-release?

A release checklist for the myanimelist-mcp Python package. It updates the package version, refreshes the local install, runs tests, commits the change, and pushes a version tag that starts publishing.

Preparing and publishing a new package release, including version bumps, verification, commits, and release tags.

It keeps the version source, local package metadata, tests, and publishing workflow in sync. It also avoids a known test failure caused by stale editable-install metadata.

How UmutKDev/myanimelist-mcp configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to UmutKDev/myanimelist-mcp. 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/UmutKDev/myanimelist-mcp/main/.claude/skills/cut-a-release/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/UmutKDev/myanimelist-mcp

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/umutkdev/myanimelist-mcp/cut-a-release/github.svg)](https://agentmods.dev/skills/umutkdev/myanimelist-mcp/cut-a-release)

Your own site

<a href="https://agentmods.dev/skills/umutkdev/myanimelist-mcp/cut-a-release"><img src="https://agentmods.dev/badge/skills/umutkdev/myanimelist-mcp/cut-a-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/skills/umutkdev/myanimelist-mcp/cut-a-release"><img src="https://agentmods.dev/badge/skills/umutkdev/myanimelist-mcp/cut-a-release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 654 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.00039	$0.00654
Opus 5	$0.00019	$0.00327
Sonnet 5	$0.00008	$0.00131
Haiku 4.5	$0.00004	$0.00065

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

Security

Grade A, and why

cut-a-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 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/cut-a-release/SKILL.md · 51 lines

How it starts

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

Cut a release

The version has one source: __version__ in src/mal_mcp/__init__.py. pyproject.toml reads it via [tool.hatch.version]. Pushing a vX.Y.Z tag triggers .github/workflows/publish.yml, which builds the UI, builds the wheel, and publishes to PyPI via Trusted Publishing.

ui/package.json is intentionally decoupled — leave it.

Steps

Pick the new semver (e.g. 0.5.1). Look at recent git log --oneline for scope.
Bump src/mal_mcp/__init__.py → __version__ = "x.y.z". uv version / uv version --bump do not work here — the version is dynamic, so uv refuses ("cannot get or set dynamic project versions"). Edit by hand.
Refresh the editable install, then test:
```
uv sync --reinstall-package myanimelist-mcp   # REQUIRED after a bump
uv run pytest
```
uv does not rebuild the editable install's dist-info when only the dynamic-version source changes, so skipping the reinstall makes test_distribution_version_matches_dunder fail with the old version. That is a local artifact, not a real defect.
Re-lock only if needed: uv lock is required when the project name or dependencies change, not for a plain version bump (the lockfile's root entry carries no version).
Commit with the repo convention — a scoped, imperative subject with the version:
- Area: short summary (x.y.z) (e.g. Schedule: keep 7 weekdays on one row (0.4.3))
- or Release x.y.z: short summary
Tag and push:
```
git tag -a vx.y.z -m "vx.y.z"
git push origin main --follow-tags
gh run watch
```
The workflow hard-fails if the tag does not match __version__, if the UI bundle is missing or is the placeholder, or if twine check --strict complains.

Do not

Do not bump ui/package.json — it is decoupled on purpose.
Do not delete or re-point a published tag. PyPI versions are immutable, so a botched release needs the next patch version, never a re-tag.
Do not upload by hand with twine. Trusted Publishing from the workflow is the only path; there is no API token anywhere, by design.
There is still no CHANGELOG and no PRs — linear history on main.

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

8d ago First seen · 51 lines · 39 tokens per session scan A 050be9e8ef43

Subscribe to this mod's changes

cut-a-release is a skill published in the GitHub repository UmutKDev/myanimelist-mcp (1 stars, last pushed 1mo ago), licensed MIT. It adds 39 tokens to every session and 654 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.

Git and workflow Releases

release-announcement

Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.

paperclipai/paperclip · 42 tokens

multi-agent-release-manager

Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.

chromium/chromium · 27 tokens

release-notes

Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.

phuryn/pm-skills · 57 tokens

pack-submit

Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.

aeonfun/aeon · 27 tokens

nvca-chart-release

Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.

NVIDIA/nvcf · 61 tokens

updater_guide

Guidance for checking for and installing Row-Bot updates.

siddsachar/row-bot · 17 tokens

myanimelist-mcp: Skill for Claude Code