housekeeping
Skill1 starsChanged 9 months agoNo licenceView on GitHub
Recovery command for when a project is in the weeds. Stops all forward work, sweeps every surface the project lives on (tickets, pages, CRM, transcripts, git, agent threads, published artifacts), finds where those surfaces now contradict each other, harvests everything the current session learned but never wrote down, then hands back a short ranked list of the next 3–5 moves. All write-backs are gated behind explicit approval. Not a status report — it reconciles and repairs. Invoked on a felt state mid-task, never on a schedule: for the end-of-day closedown that lands work and hands off, use /mise-en-place instead.
13 other projects use a version of this.
Adopted by
Most recently taken up by
- Mharbulous/probanda-devtheir own version, first seen Nov 8, 2026
- detroitwtf/claude-housekeepingtheir own version, first seen Oct 25, 2026
- ARCASSystems/FounderOStheir own version, first seen Oct 24, 2026
- buttjer/n8n-decantertheir own version, first seen Oct 21, 2026
- elfrost/ai-patchlabtheir own version, first seen Oct 13, 2026
- htlin222/dotfilestheir own version, first seen Oct 8, 2026
Other versions13 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 13
- langfuse/langfuse★ 37ksame name
- alexeykrol/claude-code-starter★ 194same name
- htlin222/dotfiles★ 78same name
- valpere/session-indexer★ 42same name
- ARCASSystems/FounderOS★ 7same name
- ImpactMojo/ImpactMojo★ 3same name
- buttjer/n8n-decanter★ 2same name
- bpappin/skills★ 1same name
- detroitwtf/claude-housekeeping★ 1same name
- elfrost/ai-patchlab★ 1same name
3 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.
In this repository10 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- ai-routerSkill
- compact-cleanSkill
- create-client-pdfSkill
- design-qa-liteSkill
- linearSkill
- mise-en-placeSkill
- preflightSkill
- prod-readiness-auditSkill
- vault-backupSkill
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 8 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 10 edited versions we read keep these.
8
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 10 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.