make-release
Skill830 starsChanged 10 days agoMITView on GitHub
Prepare a new release by updating version, changelog, and building the package
6 other projects use a version of this.
Adopted by
Most recently taken up by
- lfortran/lfortrantheir own version, first seen Nov 1, 2026
- ocicl/ocicltheir own version, first seen Oct 9, 2026
- atgreen/cl-tuitiontheir own version, first seen Oct 8, 2026
- atgreen/icltheir own version, first seen Oct 8, 2026
- quarto-dev/quarto-clitheir own version, first seen Oct 8, 2026
- hathach/tinyusbtheir own version, first seen Oct 8, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- hathach/tinyusb★ 7.3ksame name
- quarto-dev/quarto-cli★ 6.2ksame name
- lfortran/lfortran★ 1.3ksame name
- ocicl/ocicl★ 318same name
- atgreen/icl★ 200same name
- atgreen/cl-tuition★ 149same name
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 repository23 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- add-curatorSkill
- add-stablecoinSkill
- add-vault-abi-methodsSkill
- add-vault-noteSkill
- add-vault-protocolSkill
- categorise-vault-strategySkill
- check-stablecoinsSkill
- check-top-list-vaultsSkill
- check-vault-onchainSkill
- clean-up-for-prSkill
- document-curator-incidentSkill
- extract-project-logoSkill
- extract-test-setSkill
- extract-vault-protocol-logoSkill
- find-new-curatorsSkill
- fix-sphinx-docsSkill
- get-block-numberSkill
- Identify vault protocolSkill
- maintain-curatorsSkill
- monthly-vault-reportSkill
- more-vaultsSkill
- post-process-logoSkill
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 5 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
- Very specific: line 42
Create a commit with the message Preparing a release.
- Very specific: line 52
Verify the build succeeds and the output .tar.gz and .whl filenames contain the correct version number.
- Distinctive: line 56
After a successful build, tell the user:
“Common” is measured: kept by at least 6 in 10 of the 5 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
Make release
This skill prepares a new release of the web3-ethereum-defi package.
Required inputs
- Version number - The version string for the new release (e.g.,
1.1,2.0)
Steps
1. Update version in pyproject.toml
Edit the version field in pyproject.toml to the new version number.
2. Update CHANGELOG.md
- Find the
# Currentheading inCHANGELOG.md - Rename it to
# {version}(the new version number) - Append today's date in parentheses to every changelog entry in that section that is missing a date
- Insert a new
# Currentsection at the very top of the file with a single placeholder entry:
# Current
- TODO
# {version}
...existing entries...3. Create a git commit
Finish with clean-up-for-pr at the outermost task's review handoff.
Create a commit with the message Preparing a release. Push to the master.
4. Build the package
Run:
poetry buildVerify the build succeeds and the output .tar.gz and .whl filenames contain the correct version number.
5. Prompt the user
After a successful build, tell the user:
Release {version} built successfully. Please upload to PyPI manually.
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.

