Context Cleanup

The Problem

Every coding session with your agent generates countless files including plans, handoff files, logs, drafts, temp folders, build data, etc. that are relevant for the duration of that session. Yet, after your session successfully ends in a shipped feature, these files stick around, taking up your disk space and polluting your future sessions with bloated and stale context that the new session agent can easily get just by reading your latest code.

The Solution

The context-cleanup skill solves this problem by running a full sweep on your project to identify and delete the unnecessary files after you git commit your feature. Here is how it works:

• One command, and only when you type it. Type /context-cleanup in Claude Code or $context-cleanup in Codex. Neither agent starts the skill by itself.
• It stops when the work is not done. If a file that git tracks has changes that are not committed, the agent stops at the first step and names the file. It deletes nothing.
• A fresh subagent judges each leftover. A new subagent, the Sweeper, reads the project the way the next session will. It edits nothing. It gives each leftover one verdict: delete, ask, rewrite, or keep. The main agent checks each verdict before it acts.
• Short notes that are true for the code. AGENTS.md, CLAUDE.md, and other notes that only agents read keep what the project is, how to set it up, build, run, test, and deploy it, its working rules, and the gotchas of outside tools. Decisions, their reasons, and history go. Docs for your users keep their content, and their stale lines are fixed.
• Rules become checks. A written rule that a check could catch becomes a check, if you say yes. The agent adds it to a check that the project already runs, shows that the check catches a break, and removes the rule from the notes.
• Free disk space. It finds session temp folders, transcripts, worktrees, Xcode build data for project folders that are gone, and simulators that the work made. With all, it looks at every project on your Mac.

It deletes without asking only what git can bring back, or what nothing can use again: tracked files, merged branches, clean worktrees, and build data whose project folder is gone. The note rewrites and these deletions go in one commit, so git revert brings them back. It never pushes. For everything else, it asks you once, with each item and its size. It never touches a running session, a booted simulator, or a secret.

Try it: in a git repository, change one line of a tracked file and do not commit it. Type /context-cleanup. The agent stops and names the file.

FAQs

Does it delete things without asking?

Only what git can bring back, or what nothing can use again. Those deletions and the note rewrites go in one commit, so git revert brings them back. Before it deletes anything else, it lists each item with its size and asks you once.