release-cut
Skill2 starsChanged 2 days agoMITView on GitHub
Cut a tagged release - CI builds the .deb and docker image from the tag. Use for release, tag, deploy, cargo deb, ghcr, ship
- Commits and pushes
4 other projects use a version of this.
Adopted by
Most recently taken up by
- 4gray/iptvnatortheir own version, first seen Nov 1, 2026
- tony/skillstheir own version, first seen Oct 31, 2026
- thomas-powers-jr/cadencetheir own version, first seen Sep 24, 2026
- Megaprompting/torque-looptheir own version, first seen Jul 3, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- 4gray/iptvnator★ 7.8ksame name
- Megaprompting/torque-loop★ 10same name
- thomas-powers-jr/cadence★ 2same name
- tony/skills★ 0same 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 repository4 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- mcp-tokenSkill
- verify-changeSkill
The file
Files
House skill — established by the developerz.ai maintainer agent for the maintainers of this repository from this repo's own evidence, then owned by its maintainers. Correct it in place; setup never overwrites a skill that exists.
- Confirm
maingreen:bin/check. - Pick the next semver tag and bump
versionin Cargo.toml to match (CI refuses a mismatch); renamedocs/changelog/unreleased.mdtodocs/changelog/X.Y.Z.md(heading# X.Y.Z — YYYY-MM-DD, a one-paragraph summary, an Upgrading section for a breaking change), start a freshunreleased.md, and add the entry and compare link toCHANGELOG.md. git tag vX.Y.Z && git push origin vX.Y.Z.- CI on the tag gates on fmt, check (clippy + unit + e2e),
cargo audit, shellcheck and tag == Cargo.toml version; only then it builds + smoke-tests the amd64/arm64.debs (cargo deb --locked) and images, attaches the.debs +SHA256SUMSto the GitHub release (the installer refuses a release withoutSHA256SUMS), and publishes the multi-archghcr.io/developerz-ai/mcp-sshmanifest. - Report the tag pushed and the release workflow run link. fail -> never build or upload artifacts by hand; fix on main, then tag the next patch version.
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.

