linislisted

*Linis* — Filipino for "clean." Code and context files accumulate the residue of how they were built: a name here, a date there, a line quoting what someone said mid-session, a comment narrating an experiment instead of stating its settled result. None of that is wrong to have *during* a build — some of it is exactly what `remember` and the session-state file (the Minimal Banka block in `AGENTS.md`, `core/progress.md`, or `context/progress-tracker.md`, depending on tier) are supposed to capture while work is active. But once a version ships or a milestone closes, that residue stops being useful context and starts being clutter a future session has to read past to find what actually matters. This skill does not touch correctness — it never changes what code does. It only changes how it's described. ## Context Contract **Required:** files changed in the current completed milestone, resolved from the session-state file and the version-control diff. **Conditional:** a repo-wide scope, only if the user explicitly requests it · a narrower user-specified scope, respected in place of the default. **Excluded by default:** files still under active work — this skill never runs against unsettled code, by design, regardless of requested scope. **Outputs:** every proposed cleanup, listed for approval before any file is touched. **Write authority:** only the confirmed settled file(s) in scope, and only narrative/descriptive content — operational history, provenance, compatibility fac