leeklisted

# Leek > "Leek", as in leak — the vegetable. A diagnostic and hygiene pass over a Claude Code > environment: what is being wasted, what is being retained past its scope, what is > reachable from where it should not be, and what is still running after its work ended. **Leek diagnoses. Leek never remediates.** Its outputs are a report document, one GitHub issue per distinct concern, and a hand-off to `mistake-to-gate` where a finding has a repo-state predicate. It runs no cleanup, terminates no process, expires no memory and clears no cache — those are separate, deliberate acts by something else, and the reason is [ADR-0088](../../docs/adr/0088-leek-diagnoses-never-remediates.md): the scanner's own evidence says the environment is in an unexpected state, which is the worst possible moment to exercise judgment about what is safe to destroy. ## When to use - Context fills too fast; output quality degrades over a session; a session is "heavy" - Burn, spend or token usage looks disproportionate to the work done - A memory surfaced that belongs to another project, or a memory that should have expired - Caches, job workspaces, transcripts or embeddings are accumulating on disk - A session went silent, a fleet reports `blocked`, or a process will not stop - Secrets or credentials may have reached a memory store, a cache or a config file - Before adding agents, skills or MCP servers — is there room? - "Which skills have never been used?" - Periodically, as hygiene, before a campaig