Cleanup

Scan for abandoned AI agent threads across harnesses — Claude Code, OpenAI Codex CLI, Gemini CLI, Goose, OpenCode — covering old conversation transcripts and leftover per-session scratchpad directories, report them in a compact table, ask the user which to delete, then remove only what they picked. Use whenever the user wants to clean up agent sessions, threads, transcripts, or old conversations from any coding agent, complains about accumulated session junk or temp directories from agents, or asks how much space their agent history is taking — even if they only mention one session or one tool.

Scan a git repository for abandoned worktrees — the isolated working copies AI agents (Claude Code, Codex CLI, Gemini CLI, Cursor, Aider, or any other harness) create and leave behind — report each one's age, branch, and safety in a compact table, ask the user which to remove, then clean up only what they picked. Use whenever the user wants to clean up worktrees, mentions leftover / stale / agent-created worktrees or branches, notices `git worktree list` is full of junk, or complains about mystery sibling directories of their repo — even if they only mention one.

Create a new 11ai cleanup skill for any kind of idle, hanging, or abandoned resource — ports, node_modules folders, caches, agent sessions, Docker containers, stale branches, whatever the user names. Use whenever the user asks to create, make, or generate a cleanup skill for something, wants a scan-and-clean workflow for a resource, or wants to extend the 11ai cleanup skill family. The generated skill always follows the same pattern: scan → judge → report → ask → execute → verify, and never destroys anything the user didn't explicitly pick.

Scan for idle, hanging, or abandoned local ports (usually dev servers left behind by AI agents), report what's open in a compact table, ask the user which ones to clean up, then kill only the processes they picked. Use whenever the user wants to clean up ports or processes, asks "what's running on my ports", complains a port is already in use / EADDRINUSE, mentions leftover or zombie dev servers, or wants to free up a port — even if they only name a single port.

Scan for node_modules directories in stale or abandoned projects, report each one's size and age in a compact table, ask the user which to delete, then remove only what they picked. Use whenever the user wants to clean up node_modules, reclaim disk space from old JavaScript/Node projects, complains their disk is almost full, or mentions bloated / forgotten / duplicate node_modules folders — even if they only mention one project.