keep-codex-fast

Why we included this project

Codex gets heavier the longer you use it, especially if you keep long chats around, resume old threads, and work across several repos. This skill gives it a maintenance routine that defaults to doing nothing: it inspects local state and recommends a plan, and only touches anything when you explicitly say so. Before it changes anything it makes a backup, and it archives old chats rather than deleting them, rotates oversized logs, moves stale worktrees out of the way, and prunes dead project references. It can also spot the bloated thread title/preview metadata that slows down chat navigation, and it nudges you to write a handoff document before archiving a session you might want to come back to. If you want your Codex environment to stay fast without losing context, that backup-first, archive-don't-delete habit is what makes the maintenance feel safe.