release-mcp
Skill877 starsChanged 6 days agoMITView on GitHub
Release a new version of the tapo-mcp crate (MCP server), versioned independently from the tapo libraries
- Commits and pushes
2 other projects use a version of this.
Adopted by
Most recently taken up by
- fastrepl/anarlogtheir own version, first seen Oct 8, 2026
- fastrepl/hyprnotetheir 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
- fastrepl/anarlog★ 9.9ksame name
- fastrepl/hyprnote★ 9.9ksame 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 repository10 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- changelogSkill
- commitSkill
- merge-prSkill
- pre-commitSkill
- release-libsSkill
- release-openclaw-skillSkill
- review-loopSkill
- update-maturinSkill
- verify-device-supportSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 2 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Determine the new version: Read the current version from tapo-mcp/Cargo.toml.
- Very specific: line 14
Bump the version: Update the version field in tapo-mcp/Cargo.toml and both version and packages[0].identifier in tapo-mcp/server.json.
- Very specific: line 19
Add a link reference [tapo-mcp-vX.X.X]: https://github.com/mihai-dinculescu/tapo/tree/tapo-mcp-vX.X.X to the link definitions at the bottom …
- Very specific: line 21
Commit: Run /commit with message chore(tapo-mcp): release vX.X.X.
- Distinctive: line 23
Tag: Create an annotated git tag:
- Distinctive: line 29
Push: Ask the user for confirmation, then:
- Very specific: line 35
Create GitHub release: Ask the user for confirmation.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
Release tapo-mcp
Release a new version of the tapo-mcp crate.
Steps
- Determine the new version. Read the current version from
tapo-mcp/Cargo.toml. Ask the user what the new version should be if not provided. - Bump the version. Update the
versionfield intapo-mcp/Cargo.tomland bothversionandpackages[0].identifierintapo-mcp/server.json. - Update changelog. In
CHANGELOG.md:- Replace the heading
## [MCP Unreleased][Unreleased]with## [MCP vX.X.X][tapo-mcp-vX.X.X] - YYYY-MM-DD(use the current date). - Insert a new empty
## [MCP Unreleased][Unreleased]section immediately above the newly versioned section. - Add a link reference
[tapo-mcp-vX.X.X]: https://github.com/mihai-dinculescu/tapo/tree/tapo-mcp-vX.X.Xto the link definitions at the bottom of the file (right after the[Unreleased]link).
- Replace the heading
- Commit. Run
/commitwith messagechore(tapo-mcp): release vX.X.X. Tag. Create an annotated git tag:
git tag -a tapo-mcp-vX.X.X -m "tapo-mcp-vX.X.X"Push. Ask the user for confirmation, then:
git push && git push origin tapo-mcp-vX.X.XCreate GitHub release. Ask the user for confirmation. Use the content under the
## [MCP vX.X.X][tapo-mcp-vX.X.X]heading fromCHANGELOG.mdas the release body, followed by a full changelog comparison link. The previous version (vP.P.P) is the tapo-mcp tag before this release:gh release create tapo-mcp-vX.X.X --title "Tapo MCP vX.X.X" --notes "$(cat <<'EOF' <changelog content here> **Full Changelog**: https://github.com/mihai-dinculescu/tapo/compare/tapo-mcp-vP.P.P...tapo-mcp-vX.X.X EOF )"
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.

