release-status
Skill0 starsChanged 14 days agoNo licenceView on GitHub
Read-only status of the release train for Groundworks, Beltworks, Pipeworks, Wireworks, Craftworks, Fieldworks, Gearworks and Voidworks — each car's version, what ~/.m2 holds, what isn't pushed, which Showcase jar Gearworks and Voidworks are pinned at, which Groundworks the newest cars load together and whether each accepts it, and release tooling that drifts from libworks' template. Use when the user asks where a release stands, what's unreleased or unpushed, or whether the mods accept a new Groundworks, and as release-train's first step.
- Reads credentials
3 other projects use a version of this.
Adopted by
Most recently taken up by
- gtapps/claude-code-hermittheir own version, first seen Nov 7, 2026
- gtapps/hermitdtheir own version, first seen Nov 7, 2026
- flurdy/agent-skillstheir own version, first seen Aug 9, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- gtapps/claude-code-hermit★ 84same name
- gtapps/hermitd★ 84same name
- flurdy/agent-skills★ 9same 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 repository49 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- ask-mattSkill
- chief-of-staffSkill
- claude-handoffSkill
- codebase-designSkill
- code-reviewSkill
- diagnosing-bugsSkill
- domain-modelingSkill
- git-guardrails-claude-codeSkill
- grillingSkill
- grill-meSkill
- grill-with-docsSkill
- handoffSkill
- implementSkill
- implement-specSkill
- improve-codebase-architectureSkill
- loop-meSkill
- migrate-to-shoehornSkill
- prototypeSkill
- prSkill
- researchSkill
- retroSkill
- scaffold-exercisesSkill
- setup-matt-pocock-skillsSkill
- setup-pre-commitSkill
- setup-ts-deep-modulesSkill
- tddSkill
- teachSkill
- to-questionnaireSkill
- to-specSkill
- to-ticketsSkill
- triageSkill
- wait-whatSkill
- wayfinderSkill
- wizardSkill
- writing-beatsSkill
- writing-for-agentsSkill
- writing-fragmentsSkill
- writing-shapeSkill
- all-doneSkill
- conductorSkill
- diagnosing-bugsSkill
- gametest-loopSkill
- implementSkill
- iterateSkill
- quicklaunchSkill
- release-trainSkill
- stewardSkill
- template-driftSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — 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 3 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.
Reviews can't be read right now.
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.