What is release-engineer?

A release workflow for the Matimo project. It covers version changes, branches and pull requests, quality checks, review, documentation, tags, and publishing packages.

Use it when preparing a Matimo release, updating TypeScript or Python package versions, running release checks, creating the release branch or pull request, and publishing from a Git tag.

It reduces mistakes such as mismatched package versions or tags that do not trigger the intended release process. It also requires checking the repository's current configuration instead of relying on assumptions.

How tallclub/matimo configures Claude Code and Codex

Reuse

Borrowing it

Nothing to install: this file belongs to tallclub/matimo. 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/tallclub/matimo/main/.github/skills/release-engineer/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/tallclub/matimo

Made for: Claude Code, Codex.

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/tallclub/matimo/release-engineer/github.svg)](https://agentmods.dev/skills/tallclub/matimo/release-engineer)

Your own site

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

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

When invoked 2,233 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.00048	$0.02233
Opus 5.5	$0.00019	$0.00893
Sonnet 5.5	$0.00010	$0.00447
Haiku 4.5	$0.00005	$0.00223

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

Security

Grade A, and why

release-engineer 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.

.github/skills/release-engineer/SKILL.md · 239 lines

How it starts

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

Matimo Release Engineering Skill

Repository Facts (always read, never assume)

Item	How to Verify
Current TS version	Read all 11 `typescript/packages/*/package.json` — must match exactly
Current Python version	Read all 12 `python/packages/*/pyproject.toml` — note: `core` may differ from providers
Release triggers	TS: `git tag v..` → npm-release.yml; Python: `git tag python/v` → publish-python.yml
CI branch targets	See `.github/workflows/ci.yml` on_push branches
Coverage requirement	95%+ both SDKs (enforced in CI; Python fails under 95%)
Test count	Always read from `ci.yml` test-python matrix and pnpm test output — do not assume

Part 1 — Version Numbering Convention

TypeScript

Pre-release: 0.X.Y-alpha.N (example: 0.1.0-alpha.15)
Patch: 0.X.Y-alpha.N-patch.M (example: 0.1.0-alpha.14-patch.2)
Stable: 0.X.Y (example: 1.0.0)

All 11 typescript/packages/*/package.json files must have identical version strings.

Python (PEP 440)

Pattern	Example
Pre-release	`0.X.YaN` (e.g. `0.1.0a15` maps to TS `0.1.0-alpha.15`)
Patch	`0.X.YaN.postM` (e.g. `0.1.0a14.post2`)
Stable	`0.X.Y` (e.g. `1.0.0`)

All 12 python/packages/*/pyproject.toml files must have the same base version. Exception: python/packages/core may have a .postN increment separate from other packages; read it before assuming consistency.

Files to bump every release:

typescript/packages/core/package.json
typescript/packages/cli/package.json
typescript/packages/slack/package.json
typescript/packages/github/package.json
typescript/packages/gmail/package.json
typescript/packages/notion/package.json
typescript/packages/postgres/package.json
typescript/packages/twilio/package.json
typescript/packages/hubspot/package.json
typescript/packages/mailchimp/package.json
typescript/packages/bruno/package.json

python/packages/core/pyproject.toml
python/packages/cli/pyproject.toml
python/packages/matimo/pyproject.toml
python/packages/slack/pyproject.toml
python/packages/github/pyproject.toml
python/packages/gmail/pyproject.toml
python/packages/notion/pyproject.toml
python/packages/postgres/pyproject.toml
python/packages/twilio/pyproject.toml
python/packages/hubspot/pyproject.toml
python/packages/mailchimp/pyproject.toml
python/packages/bruno/pyproject.toml

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

1mo ago First seen · 239 lines · 48 tokens per session scan A 3a6260877a6a

Subscribe to this mod's changes

release-engineer is a skill published in the GitHub repository tallclub/matimo (18 stars, last pushed yesterday), licensed MIT. It adds 48 tokens to every session and 2,233 once invoked, about $0.0002 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-10-05.

Git and workflow Project management Releases

release-engineer next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
release-engineertallclub/matimo	Skill	18	yesterday	MIT	A	48	Claude Code, Codex
release-announcementpaperclipai/paperclip	Skill	111k	today	MIT	A	42	Claude Code, Codex
releasethedotmack/claude-mem	Skill	114k	today	Apache-2.0	A	13	Claude Code
release-notesphuryn/pm-skills	Skill	28k	8d ago	MIT	A	57	Claude Code
multi-agent-release-managerchromium/chromium	Skill	25k	today	BSD-3-Clause	A	27	Claude Code, Codex
pack-submitaeonfun/aeon	Skill	788	yesterday	MIT	A	27	Claude Code, Codex
updater_guidesiddsachar/row-bot	Skill	1.7k	today	Apache-2.0	A	22	Claude Code, Codex

matimo: Skill for Claude Code