github-release
Skill4 starsChanged 34 days agoLicence not identifiedView on GitHub
Cut a release of this project end to end — mirror CI locally, bump the version, update the changelog, commit, create the annotated vX.Y.Z tag, push the branch and tag, and publish the GitHub Release with brief English bullet notes. Use this skill whenever the user says "release", "cut/publish a release", "bump the version", "tag a version", "ship vX.Y.Z", "make the release/notes", or asks for GitHub release notes for this repo — even if they name only one step, because the steps only make sense as one sequence and a half-done release (tag without release, release without a bump) is a state the repo should never be left in.
- Commits and pushes
9 other projects use a version of this.
Adopted by
Most recently taken up by
- h2cone/agent-packstheir own version, first seen Nov 1, 2026
- github/awesome-copilottheir own version, first seen Oct 25, 2026
- lamxy/agent-prompt-rules-systemtheir own version, first seen Oct 20, 2026
- decentpaste/decentpastetheir own version, first seen Oct 8, 2026
- BenedictKing/ccxtheir own version, first seen Sep 17, 2026
- hjdspace/SpaceCodetheir own version, first seen Jul 21, 2026
Other versions9 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 9
- github/awesome-copilot★ 41ksame name
- BenedictKing/ccx★ 4ksame name
- decentpaste/decentpaste★ 249same name
- atman-33/multi-agent-ff15★ 4same name
- hjdspace/SpaceCode★ 4same name
- lamxy/agent-prompt-rules-system★ 4same name
- gauravv-g/claude-skills-collection★ 1same name
- h2cone/agent-packs★ 0same name
- zarvent/v2m-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 repository3 other files it gives its agents.
- AGENTS.mdAGENTS.md
- mcp-designSkill
- rust-repo-structureSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
15 rules. 0 are common, 10 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
10
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 7 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.
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.