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
- naomiaro/waveform-playlisttheir own version, first seen Nov 16, 2026
- osmlab/name-suggestion-indextheir own version, first seen Nov 16, 2026
- vulnerability-lookup/vulnerability-lookuptheir own version, first seen Nov 16, 2026
- ClickHouse/mcp-clickhousetheir own version, first seen Nov 16, 2026
- bpatrik/pigallery2their own version, first seen Nov 16, 2026
- Shasnow/StarRailAssistanttheir own version, first seen Nov 16, 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
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
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 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
parcadeiSkillagent-context-isolation
Agent Context Isolation
Also in 3 projects that use this
- +3 more from Grinv
Other versions193 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 193
- paperclipai/paperclip★ 114ksame name
- modelcontextprotocol/servers★ 92ksame name
- remotion-dev/remotion★ 73ksame name
- traefik/traefik★ 66ksame name
- usememos/memos★ 64ksame name
- tw93/Pake★ 64ksame name
- AmruthPillai/Reactive-Resume★ 46ksame name
- amruthpillai/reactive-resume★ 46ksame name
- reactive-resume/reactive-resume★ 46ksame name
- Yeachan-Heo/oh-my-claudecode★ 41ksame name
183 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.
In this repository5 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
- python-authoringSkill
- skillz-self-updateSkill
- skillzSkill
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
- Very specific: line 34
Read the ## [Unreleased] section of packages/fromargs/CHANGELOG.md.
- Very specific: line 36
Stop when the tag fromargs-v<version> exists on origin or https://pypi.org/pypi/fromargs/<version>/json returns 200.
- Very specific: line 40
Create the branch chore/fromargs-release-<version>.
- Very specific: line 42
Update the link references at the end of the CHANGELOG.
- Very specific: line 44
When the minor version changes, set the fromargs range in pyproject.toml and packages/wedge/pyproject.toml to …
- Very specific: line 58
Run just fromargs-release-notes <version> and read the output.
- Very specific: line 59
Run uv build --package fromargs --no-sources --out-dir <temp dir> and uvx twine check <temp dir>/*.
- Very specific: line 60
Run just build. Stop on a new failure.
- Very specific: line 61
Commit the named files as chore(fromargs): release <version>.
- Distinctive: line 65
Wait for every PR check to pass.
- Distinctive: line 68
When the merge date differs from the CHANGELOG date, fix the date in a new PR before you tag.
- Distinctive: line 73
Create and push an annotated tag on the merge commit:
- Very specific: line 92
Read https://pypi.org/pypi/fromargs/<version>/json.
- Very specific: line 93
Read gh release view fromargs-v<version>.
- Distinctive: line 98
Never move, delete, or re-push a published tag.
- Distinctive: line 99
When the build job fails, no upload happened.
- Very specific: line 100
When PyPI has the version but the github-release job failed, re-run only the failed job with gh run rerun <run-id> --failed.
- Distinctive: line 101
Never approve a deployment for a run whose tag does not point at the reviewed merge commit.
“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.
Files
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.mdis 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.ymlruns on afromargs-v*tag. Its build job requires the tag commit onmainand the tag version equal topackages/fromargs/pyproject.toml.- The
publishjob waits for thepypienvironment approval, then uploads with trusted publishing. - The
github-releasejob creates the GitHub release with--latest=false. It fails when the tag moved after the build. - The wedge bundles and the
cheese-caveexample lock embed the fromargs source, so a version change needs a rebuild.
1. Preflight
- Switch to
main, pull with--ff-only, and require a clean tree. - Read the
## [Unreleased]section ofpackages/fromargs/CHANGELOG.md. Stop when it is empty. - Choose the version. Use the argument when the user gives one. Otherwise, propose the next minor version for a
0.xrelease with a Breaking entry, and the next patch version for other changes. Confirm the proposed version with the user. - Stop when the tag
fromargs-v<version>exists onoriginorhttps://pypi.org/pypi/fromargs/<version>/jsonreturns 200.
2. Prepare the release PR
- Create the branch
chore/fromargs-release-<version>. - In
packages/fromargs/CHANGELOG.md, move theUnreleasedentries under## [<version>] - <YYYY-MM-DD>with today's date. Keep an empty## [Unreleased]heading. - Update the link references at the end of the CHANGELOG.
[Unreleased]comparesfromargs-v<version>...HEAD. Add[<version>]to compare the previous tag withfromargs-v<version>. - Set
version = "<version>"inpackages/fromargs/pyproject.toml. - When the minor version changes, set the
fromargsrange inpyproject.tomlandpackages/wedge/pyproject.tomlto>=<major>.<minor>.0,<<major>.<next minor>. Relock the workspace with the uv version that the workflow pins in its
setup-uvstep, so the lockfilerevisionstays compatible with CI:uvx uv@<ci-uv-version> lockRebuild 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- Run
just fromargs-release-notes <version>and read the output. It must show the complete new section. - Run
uv build --package fromargs --no-sources --out-dir <temp dir>anduvx twine check <temp dir>/*. - Run
just build. Stop on a new failure. Compare any failure with a cleanmaincheckout before you call it a baseline failure. - Commit the named files as
chore(fromargs): release <version>. Push the branch and open a PR againstmain. Put the release notes and the post-merge steps in the PR body.
3. Merge
- Wait for every PR check to pass. Resolve or answer every review thread.
- Get explicit user approval to merge, unless the user asked for the complete release in this session.
- Squash-merge with
gh pr merge <n> --squash --match-head-commit <sha>. Record the merge commit SHA. - When the merge date differs from the CHANGELOG date, fix the date in a new PR before you tag.
4. Tag and approve
- Fetch
main. Confirm that the merge commit is onorigin/mainand that it has the new version and CHANGELOG section. 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>- Find the
publish fromargsrun for the tag. Wait until the build job passes and the run waits on thepypienvironment. 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
- Watch the run to completion. Every job must succeed.
- Read
https://pypi.org/pypi/fromargs/<version>/json. Confirm the version, the dependency ranges, and one wheel and one sdist. - 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. - 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-releasejob failed, re-run only the failed job withgh 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.
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.

