release
Skill7 starsChanged 12 days agoApache-2.0View on GitHub
Cut a transformers-mic (tmic) release to PyPI. Updates CHANGELOG.md and the single pyproject version, runs the tests and a packaged smoke test, pushes the vX.Y-release branch and, after confirmation, the vX.Y.Z tag that publishes through GitHub OIDC, then opens the next version on main. Use when asked to release tmic, cut a version, or ship X.Y.Z.
- Installs packages
- Commits and pushes
196 other projects use a version of this.
Adopted by
Most recently taken up by
- zxcvbn-ts/zxcvbntheir own version, first seen Nov 9, 2026
- TechbeeAT/jtxBoardtheir own version, first seen Nov 9, 2026
- ddnexus/pagytheir own version, first seen Nov 9, 2026
- zerx-lab/FluxDowntheir own version, first seen Nov 9, 2026
- orioledb/orioledbtheir own version, first seen Nov 9, 2026
- AmruthPillai/Reactive-Resumetheir own version, first seen Nov 8, 2026
Used with
Projects with it also use create-agent-adapter, changelog-style and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
MicrosoftSkillcreate-agent-adapter
Technical guide for creating a new Paperclip agent adapter. Use when building a new adapter package, adding support for a new AI coding tool (e.g. a new CLI agent, API-based agent, or custom process), or when modifying the adapter system. Covers the required interfaces, module structure, registration points, and conventions derived from the existing claude-local and codex-local adapters.
Also in 5 projects that use this
GrinvSkillchangelog-style
Turn a commit range into CHANGELOG.md entries following common-changelog style. Use when finishing a PR or cutting a release, to write/fix the [Unreleased] section's entries — moving [Unreleased] under a new dated version heading is a separate, automated step (see the release skill / scripts/sync-version.ts), not this skill's job.
Also in 4 projects that use this
GrinvSkilldocs-consistency-check
Check README/manifest.json/server.json/CHANGELOG.md/AGENTS.md and docs/*.md for drift against the actual registered tools and source. Use after adding, renaming, or removing a tool, or as part of a live-audit pass.
Also in 4 projects that use this
Microsoft AzureSkillcomponent-release
Prepares a verifiable Agent Landing Zone UI release. Use for release branches, VERSION, changelog entries, tags, release notes, and compatibility evidence; never publish without explicit human approval.
Also in 4 projects that use this
Microsoft AzureSkilldocumentation-consistency
Keeps AI Landing Zone contributor, user, and operator documentation aligned with shipped Bicep behavior. Use for parameters, defaults, outputs, topology, deployment flow, operations, or releases.
Also in 8 projects that use this
rivet-devSkilllaunch-graphics
Generate agentOS marketing/launch graphics (launch & social heroes, code-snippet cards) from the committed generators in docs-internal/graphics. Use when asked to make, update, or render an agentOS launch image, social image, "agentOS Apps" graphic, or technical code-snippet image.
Also in 3 projects that use this
- +3 more from Grinv
Other versions196 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 196
- paperclipai/paperclip★ 112ksame name
- modelcontextprotocol/servers★ 92ksame name
- remotion-dev/remotion★ 72ksame name
- traefik/traefik★ 65ksame name
- usememos/memos★ 64ksame name
- tw93/Pake★ 63ksame name
- AmruthPillai/Reactive-Resume★ 45ksame name
- amruthpillai/reactive-resume★ 45ksame name
- reactive-resume/reactive-resume★ 45ksame name
- Yeachan-Heo/oh-my-claude-sisyphus★ 41ksame name
186 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.
0
Common
Most of the 186 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
Start from a clean, up-to-date main.
- Very specific: line 18
Never run twine upload. Publishing is CI-only, from the tag.
- Very specific: line 29
Changelog: Add ## [X.Y.Z] - YYYY-MM-DD (today) above the previous release in CHANGELOG.md, from git log vPREV..HEAD --oneline.
“Common” is measured: kept by at least 6 in 10 of the 186 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Release transformers-mic
The procedure and its reasons are in docs/release.md; this is the checklist. CI publishes: pushing the vX.Y.Z
tag runs .github/workflows/release.yml, which builds, tests and uploads to PyPI through trusted publishing.
Input
<version>:X.Y.Z, orX.Y.ZrcNfor a pre-release.
Rules
- Start from a clean, up-to-date
main. Never release uncommitted changes. - Never run
twine upload. Publishing is CI-only, from the tag. - Ask the user before pushing the tag. It publishes, and a PyPI version can never be reused.
pyproject.toml[project].versionis the only version string. Do not add another, and do not bumpDEFAULT_BASE_VERSIONinsrc/transformers_mic/_version.py.- Land changes on
mainthrough PRs, not direct pushes.
Steps
- Preflight.
git fetch && git statusonmain;<version>must be above the latest tag (git tag). For a first release, confirm with the user that the PyPI pending publisher and thepypi-releaseGitHub environment exist (gh api repos/huggingface/transformers-mic/environments). - Changelog. Add
## [X.Y.Z] - YYYY-MM-DD(today) above the previous release inCHANGELOG.md, fromgit log vPREV..HEAD --oneline. Use### Added/### Changed/### Fixed; one line per user-visible change, linking PRs where useful. Fold an existing## [Unreleased]section into it. - Version. Set
[project].versioninpyproject.tomlto<version>. - Test and build in a Python 3.11 venv with
pip install -e ".[runtime,dev]":make test make build-release python -m twine check --strict dist/* - Smoke-test the wheel from outside the checkout:
python3.11 -m venv /tmp/tmic-release && /tmp/tmic-release/bin/pip install dist/*.whl cd /tmp && /tmp/tmic-release/bin/tmic --version && /tmp/tmic-release/bin/tmic run --help > /dev/nulltmic --versionmust print exactly<version>. - Land the bump on
main: branchrelease-X.Y.Z, commitRelease X.Y.Z, PR, squash-merge. - Release branch. New minor:
git switch main && git pull --ff-only && git switch -c vX.Y-release && git push -u origin vX.Y-release. Patch: fast-forward the existing branch frommainand push. Wait for theReleaserun on the branch to pass (gh run list --repo huggingface/transformers-mic --workflow release.yml). - Tag, after the user confirms, from
vX.Y-release:
The publish job may wait for a reviewer on thegit tag vX.Y.Z -m "Release vX.Y.Z" && git push origin vX.Y.Z gh run watch --repo huggingface/transformers-micpypi-releaseenvironment; say so instead of waiting silently. - Verify in a fresh venv:
pip install "transformers-mic==X.Y.Z"thentmic --version. - Next version. PR on
main:[project].versiontoX.Y.(Z+1)and an empty## [Unreleased]heading inCHANGELOG.md, commitStarting version NEXT. Not tagged, not merged into the release branch.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

