Empty litter
Cat-grade engineering skills for coding agents. Spec → tickets → TDD in worktrees, plus repo hygiene. No slop.
npx -y skills add ai-meow/felix-skills --skill empty-litterAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 20 days oldThe repository was created 20 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Cleaning session for the repository. Scans for bad practices and architectural friction — dead code, duplication, shallow modules, inconsistent patterns, config drift, untested seams — then fixes what the user picks. Use when the user says empty-litter, wants to clean the repo, remove tech debt, or improve the architecture.
SKILL.md
2.0 KB, as published. Nobody here has run it
empty-litter 🧹
Clean the litter box. Find what stinks, remove it. Read ../no-slop.md first.
Scan
Explore the repo (structure, hot files via git log --format= --name-only | sort | uniq -c | sort -rg | head -20, tests, configs). Look for, in priority order:
- Dead weight — unused exports, unreferenced files, commented-out code, stale deps (
knip/depcheck/ts-pruneif available). - Duplication — copy-pasted logic across modules (use
jscpdif available). - Shallow modules — files that only forward calls; interfaces wider than their implementation.
- Pattern drift — three ways of doing the same thing (fetching, error handling, validation).
- Untested seams — core logic only reachable through UI or IO.
- Config rot — unused env vars, dead feature flags, CI steps that do nothing.
Report
Output a ranked list, max 7 items, one line each:
1. [DELETE] src/legacy/sync.ts — unreferenced since a1b2c3 (−400 loc)
2. [DEDUP] price formatting ×4 (cart, invoice, email, admin)
3. [SEAM] discount logic only testable through checkout route
No HTML report. No essay. Effort estimate only if asked.
Act
The user picks items by number. For each:
- Work on the current branch unless the user asks for a worktree.
- Deleting beats refactoring. Refactoring beats rewriting.
- Behavior must not change: run the test suite before and after. If a seam has no tests, add the minimal test that locks current behavior first.
- One commit per item, message prefix
litter:.
Stop after the picked items. Do not "keep going while you're at it".
Gives 1 of the 12 instructions most refactoring skills give
Counted across 521 of the 525 authors here whose files we hold, read 2026-08-06
- run tests after each changehere, and in 59 of 521, across 56 files
- write tests before refactoringin 27 of 521, across 24 files
- preserve external behaviorin 26 of 521, across 22 files
- remove dead codein 25 of 521, across 24 files
- make small incremental changesin 20 of 521, across 17 files
- break the implementation into tiny commitsin 18 of 521, across 5 files
- ask the user about alternative optionsin 17 of 521, across 4 files
- create a GitHub issue with the planin 17 of 521, across 4 files
- explore the repository to verify assertionsin 17 of 521, across 4 files
- interview the user about the refactorin 16 of 521, across 3 files
- check the codebase for test coveragein 16 of 521, across 3 files
- refactor one thing at a timein 16 of 521, across 12 files
Said here and by no other author read
- read no-slop.md first
- scan repo structure hot files tests and configs
- prioritize dead weight first
- prioritize duplication second
- prioritize shallow modules third
- prioritize pattern drift fourth
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.