agentleFS
paulnsorensenpaulnsorensen/skillz-that-grillz/.agents/skills/release/SKILL.md

release

Skill1 starsChanged 23 days agoMITView on GitHub

Release the fromargs Python distribution to PyPI and GitHub from this repository. Prepares the CHANGELOG, version, pins, locks, and wedge bundles in a release PR, then merges it, tags `fromargs-v<version>`, approves the `pypi` deployment, and verifies the published artifacts. Use when a maintainer asks to "release fromargs", "cut a fromargs release", "publish fromargs <version>", or invokes /release. Do NOT use for the published skills or the wedge action.

  • Commits and pushes

193 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

  • 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

  • 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

    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

  • parcadeiSkill

    agent-context-isolation

    Agent Context Isolation

    Also in 3 projects that use this

  • +3 more from Grinv

The file

Show its rules and text

We split this skill into the rules it gives an agent

18 rules. 0 are common, 6 are distinctive, and 12 are very specific to this project.

  • 0

    Common

    Most of the 183 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 12

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read the ## [Unreleased] section of packages/fromargs/CHANGELOG.md.

    line 34
  2. Very specific:

    Stop when the tag fromargs-v<version> exists on origin or https://pypi.org/pypi/fromargs/<version>/json returns 200.

    line 36
  3. Very specific:

    Create the branch chore/fromargs-release-<version>.

    line 40
  4. Very specific:

    Update the link references at the end of the CHANGELOG.

    line 42
  5. Very specific:

    When the minor version changes, set the fromargs range in pyproject.toml and packages/wedge/pyproject.toml to …

    line 44
  6. Very specific:

    Run just fromargs-release-notes <version> and read the output.

    line 58
  7. Very specific:

    Run uv build --package fromargs --no-sources --out-dir <temp dir> and uvx twine check <temp dir>/*.

    line 59
  8. Very specific:

    Run just build. Stop on a new failure.

    line 60
  9. Very specific:

    Commit the named files as chore(fromargs): release <version>.

    line 61
  10. Distinctive:

    Wait for every PR check to pass.

    line 65
  11. Distinctive:

    When the merge date differs from the CHANGELOG date, fix the date in a new PR before you tag.

    line 68
  12. Distinctive:

    Create and push an annotated tag on the merge commit:

    line 73
  13. Very specific:

    Read https://pypi.org/pypi/fromargs/<version>/json.

    line 92
  14. Very specific:

    Read gh release view fromargs-v<version>.

    line 93
  15. Distinctive:

    Never move, delete, or re-push a published tag.

    line 98
  16. Distinctive:

    When the build job fails, no upload happened.

    line 99
  17. Very specific:

    When PyPI has the version but the github-release job failed, re-run only the failed job with gh run rerun <run-id> --failed.

    line 100
  18. Distinctive:

    Never approve a deployment for a run whose tag does not point at the reviewed merge commit.

    line 101

“Common” is measured: kept by at least 6 in 10 of the 183 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 fromargs

This is a repository-local skill for skillz-that-grillz. It lives under .agents/skills/release/, with a .claude/skills/ symlink for Claude Code. metadata.internal: true hides it from npx skills add. Do not move it into the published skills/ tree.

A tag push publishes to PyPI after one approval, and PyPI never accepts the same version twice. Treat the tag push and the approval as irreversible.

Release contract

  • packages/fromargs/CHANGELOG.md is the only source of release notes. just fromargs-release-notes <version> prints one section and fails when it is missing or empty.
  • .github/workflows/publish-fromargs.yml runs on a fromargs-v* tag. Its build job requires the tag commit on main and the tag version equal to packages/fromargs/pyproject.toml.
  • The publish job waits for the pypi environment approval, then uploads with trusted publishing.
  • The github-release job creates the GitHub release with --latest=false. It fails when the tag moved after the build.
  • The wedge bundles and the cheese-cave example lock embed the fromargs source, so a version change needs a rebuild.

1. Preflight

  1. Switch to main, pull with --ff-only, and require a clean tree.
  2. Read the ## [Unreleased] section of packages/fromargs/CHANGELOG.md. Stop when it is empty.
  3. Choose the version. Use the argument when the user gives one. Otherwise, propose the next minor version for a 0.x release with a Breaking entry, and the next patch version for other changes. Confirm the proposed version with the user.
  4. Stop when the tag fromargs-v<version> exists on origin or https://pypi.org/pypi/fromargs/<version>/json returns 200.

2. Prepare the release PR

  1. Create the branch chore/fromargs-release-<version>.
  2. In packages/fromargs/CHANGELOG.md, move the Unreleased entries under ## [<version>] - <YYYY-MM-DD> with today's date. Keep an empty ## [Unreleased] heading.
  3. Update the link references at the end of the CHANGELOG. [Unreleased] compares fromargs-v<version>...HEAD. Add [<version>] to compare the previous tag with fromargs-v<version>.
  4. Set version = "<version>" in packages/fromargs/pyproject.toml.
  5. When the minor version changes, set the fromargs range in pyproject.toml and packages/wedge/pyproject.toml to >=<major>.<minor>.0,<<major>.<next minor>.
  6. Relock the workspace with the uv version that the workflow pins in its setup-uv step, so the lockfile revision stays compatible with CI:

    uvx uv@<ci-uv-version> lock
  7. Rebuild the artifacts that embed fromargs:

    uv run --locked --project packages/wedge wedge lock --root packages/wedge/examples/skills
    uv run --locked --project packages/wedge wedge bundle skills/skillz
  8. Run just fromargs-release-notes <version> and read the output. It must show the complete new section.
  9. Run uv build --package fromargs --no-sources --out-dir <temp dir> and uvx twine check <temp dir>/*.
  10. Run just build. Stop on a new failure. Compare any failure with a clean main checkout before you call it a baseline failure.
  11. Commit the named files as chore(fromargs): release <version>. Push the branch and open a PR against main. Put the release notes and the post-merge steps in the PR body.

3. Merge

  1. Wait for every PR check to pass. Resolve or answer every review thread.
  2. Get explicit user approval to merge, unless the user asked for the complete release in this session.
  3. Squash-merge with gh pr merge <n> --squash --match-head-commit <sha>. Record the merge commit SHA.
  4. When the merge date differs from the CHANGELOG date, fix the date in a new PR before you tag.

4. Tag and approve

  1. Fetch main. Confirm that the merge commit is on origin/main and that it has the new version and CHANGELOG section.
  2. Create and push an annotated tag on the merge commit:

    git tag -a fromargs-v<version> <merge-sha> -m "Release fromargs <version>"
    git push origin fromargs-v<version>
  3. Find the publish fromargs run for the tag. Wait until the build job passes and the run waits on the pypi environment.
  4. Approve the deployment only after the user approves it, unless the user asked for the complete release in this session:

    gh api repos/<owner>/<repo>/actions/runs/<run-id>/pending_deployments \
      -X POST -F "environment_ids[]=<pypi-env-id>" -f state=approved \
      -f comment="Approve fromargs <version>"

5. Verify

  1. Watch the run to completion. Every job must succeed.
  2. Read https://pypi.org/pypi/fromargs/<version>/json. Confirm the version, the dependency ranges, and one wheel and one sdist.
  3. Read gh release view fromargs-v<version>. Confirm that it is not a draft, that its body starts with the CHANGELOG section, and that both dist files are attached.
  4. Confirm that the repository's latest release did not change.

Failure rules

  • Never move, delete, or re-push a published tag. A new fix needs a new patch version.
  • When the build job fails, no upload happened. Fix the cause on main, delete the unpublished tag only with user approval, and tag again.
  • When PyPI has the version but the github-release job failed, re-run only the failed job with gh run rerun <run-id> --failed.
  • Never approve a deployment for a run whose tag does not point at the reviewed merge commit.

Report

Report the PR, the merge commit, the tag, the workflow run, the PyPI URL, and the GitHub release URL. Name every check that did not run.

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.