update-version
Skill77 starsChanged 20 days agoMITView on GitHub
Bump the HAEO version consistently across pyproject.toml, custom_components/haeo/manifest.json, and uv.lock. Use when asked to set, bump, or release a version, when the version consistency gate fails, or when a release tag does not match the project version.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- ZingerLittleBee/dockerman.apptheir own version, first seen Oct 8, 2026
- remotion-dev/remotiontheir own version, first seen Oct 8, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- remotion-dev/remotion★ 73ksame name
- ZingerLittleBee/dockerman.app★ 345same 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 repository18 other files it gives its agents.
- AGENTS.mdAGENTS.md
- agent-setupSkill
- config-flowSkill
- coverageSkill
- documentationSkill
- elementsSkill
- explain-planSkill
- integrationSkill
- lintSkill
- manifestSkill
- modelSkill
- performanceSkill
- pythonSkill
- release-notesSkill
- scenariosSkill
- testingSkill
- translationsSkill
- update-docsSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 0 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Update the project version number to $VERSION.
- Very specific: line 10
If $VERSION starts with v, use the version without the leading v in project files.
- Very specific: line 28
Run uv lock to regenerate the lockfile with the new version.
- Very specific: line 30
Run uv run check version to confirm the two files agree.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Update version
Update the project version number to $VERSION.
If $VERSION starts with v, use the version without the leading v in project files.
The version is PEP 440 style, X.Y.Z with an optional rcN, aN, or bN suffix, such as 0.5.0rc1.
The release workflow rejects a tag in any other form, or one that does not match both files.
Update
pyproject.toml:version = "$VERSION"Update
custom_components/haeo/manifest.json:{ "version": "$VERSION" }- Run
uv lockto regenerate the lockfile with the new version. - Run
uv run check versionto confirm the two files agree.
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.

