agentleFS
Hugging FaceKnown publisherhuggingface/transformers-mic/.ai/skills/release/SKILL.md

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

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.
  • MicrosoftSkill

    create-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

  • GrinvSkill

    changelog-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

  • GrinvSkill

    docs-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 AzureSkill

    component-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 AzureSkill

    documentation-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-devSkill

    launch-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

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
  1. Distinctive:

    Start from a clean, up-to-date main.

    line 17
  2. Very specific:

    Never run twine upload. Publishing is CI-only, from the tag.

    line 18
  3. Very specific:

    Changelog: Add ## [X.Y.Z] - YYYY-MM-DD (today) above the previous release in CHANGELOG.md, from git log vPREV..HEAD --oneline.

    line 29

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

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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, or X.Y.ZrcN for 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].version is the only version string. Do not add another, and do not bump DEFAULT_BASE_VERSION in src/transformers_mic/_version.py.
  • Land changes on main through PRs, not direct pushes.

Steps

  1. Preflight. git fetch && git status on main; <version> must be above the latest tag (git tag). For a first release, confirm with the user that the PyPI pending publisher and the pypi-release GitHub environment exist (gh api repos/huggingface/transformers-mic/environments).
  2. Changelog. Add ## [X.Y.Z] - YYYY-MM-DD (today) above the previous release in CHANGELOG.md, from git 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.
  3. Version. Set [project].version in pyproject.toml to <version>.
  4. 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/*
  5. 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/null
    tmic --version must print exactly <version>.
  6. Land the bump on main: branch release-X.Y.Z, commit Release X.Y.Z, PR, squash-merge.
  7. 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 from main and push. Wait for the Release run on the branch to pass (gh run list --repo huggingface/transformers-mic --workflow release.yml).
  8. Tag, after the user confirms, from vX.Y-release:
    git tag vX.Y.Z -m "Release vX.Y.Z" && git push origin vX.Y.Z
    gh run watch --repo huggingface/transformers-mic
    The publish job may wait for a reviewer on the pypi-release environment; say so instead of waiting silently.
  9. Verify in a fresh venv: pip install "transformers-mic==X.Y.Z" then tmic --version.
  10. Next version. PR on main: [project].version to X.Y.(Z+1) and an empty ## [Unreleased] heading in CHANGELOG.md, commit Starting version NEXT. Not tagged, not merged into the release branch.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.