maintain
Skill0 starsChanged 5 days agoMITView on GitHub
Periodic pruning and cap enforcement - lessons, line budgets, skills, dependencies, changelog freshness. Use monthly, on request, or when a cap is exceeded; never mid-task.
20 other projects use a version of this.
Adopted by
Most recently taken up by
- inoio/agents-sandboxtheir own version, first seen Nov 8, 2026
- devantler-tech/ksailtheir own version, first seen Nov 7, 2026
- jamesm-dev/tateru.devtheir own version, first seen Nov 1, 2026
- exmergo/dextheir own version, first seen Oct 31, 2026
- constant-itis/mycelium-memorytheir own version, first seen Oct 20, 2026
- garrytan/gbraintheir own version, first seen Oct 17, 2026
Used with
Projects with it also use release.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
MicrosoftSkillrelease
Use ONLY when the user explicitly asks to cut/publish a Huabu desktop release or tag a version. Performs an outward action — bumps the version in apps/desktop/package.json, commits + annotated-tags vX.Y.Z, and pushes the branch + tag. That tag push auto-builds the macOS/Windows installers and publishes a GitHub Release. Provides `status`, `bump`, `tag-push`, and a one-command `run` (bump → tag-push).
Also in 4 projects that use this
Other versions20 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 20
- garrytan/gbrain★ 32ksame name
- slopus/happy★ 25ksame name
- PhilipK/BoilR★ 1.9ksame name
- GlassHaven/Haven★ 1.4ksame name
- GlassOnTin/Haven★ 1.4ksame name
- iovisor/ubpf★ 996same name
- everruns/bashkit★ 325same name
- devantler-tech/ksail★ 164same name
- exmergo/dex★ 116same name
- inoio/agents-sandbox★ 84same name
10 more not listed
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.
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 19 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.
- Common
- Distinctive
- Very specific
- Very specific: line 6
Follow docs/procedures/maintain.md exactly.
“Common” is measured: kept by at least 6 in 10 of the 19 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.
Files
Follow docs/procedures/maintain.md exactly. Archive on evidence, never on vibes; archival is a move to .archive/ with a one-line reason.
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.