菜单
Finds old, empty, or tiny Claude Code session files that are candidates for deletion. Use when the user wants to clean up sessions, free disk space, says "clean up old sessions", or asks about session storage usage.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Health-checks Claude Code memories for staleness, broken links, orphaned files, expired dates, missing frontmatter, and duplicates. Offers two-tier fixes: deterministic auto-fixes and AI-assisted corrections. Use when the user asks to clean up memories, check memory health, find stale memories, or audit their stored knowledge. Also triggered by: "memory health", "stale memories", "clean up memories", "memory audit".
Searches across all Claude Code memory file contents by keyword. Use when the user asks to find something in their memories, search stored knowledge, or locate a specific memory by content rather than name. Also triggered by: "search memories for", "find in memories", "which memory mentions".
Searches and lists all Claude Code memories across projects. Use when the user asks what memories exist, wants to see stored knowledge, asks "what do you remember", or wants an overview of their memory files. Also triggered by: "list memories", "show memories", "what's in my memory".
Delete a Claude Code session file, with optional cleanup of associated task lists and tasks. Warns about orphaned tasks before deleting. Use when the user says "delete session", "remove session", or wants to clean up a specific session.
Show detailed information about a Claude Code session including stats, token usage, models used, tools called, associated tasks, and conversation messages. Use when the user says "show session", "session details", "what happened in session X".
Compares two Claude Code sessions — shows what changed in files, tools used, branches, and topics. Use when the user says "what changed between sessions", "diff sessions", "compare yesterday and today", or wants to understand how work evolved across sessions.
| name | session-cleanup |
| description | Finds old, empty, or tiny Claude Code session files that are candidates for deletion. Use when the user wants to clean up sessions, free disk space, says "clean up old sessions", or asks about session storage usage. |
Find session files that are candidates for cleanup.
bun run ${CLAUDE_PLUGIN_ROOT}/lib/session-store.ts cleanup --min-messages 3
To also find old sessions:
bun run ${CLAUDE_PLUGIN_ROOT}/lib/session-store.ts cleanup --older-than 30d --min-messages 3
The script outputs a JSON object with candidates array and total_size_bytes. Present as a table:
| # | Session ID | Project | Reason | Messages | Age | Size |
|---|
Show the total reclaimable space.
NEVER delete without explicit user confirmation. Present the list and ask:
"Found N sessions (X total) that could be cleaned up. Want me to delete them? (yes/no)"
If confirmed, delete each session using the delete command:
bun run ${CLAUDE_PLUGIN_ROOT}/lib/session-store.ts delete-session <session-id>
This will also report any task lists that become orphaned.
For manual deletion, the file path is also shown:
rm "<path-to-session.jsonl>"
Report each deletion. If the user wants to keep some, ask which ones to skip.
After cleanup, check for task lists that no longer have matching sessions:
bun run ${CLAUDE_PLUGIN_ROOT}/lib/session-store.ts orphan-task-lists
If orphans are found, present them:
| Task List ID | Tasks | Last Modified |
|---|
Ask: "Found N orphan task lists with no matching session. Delete them? (yes/no/select)"
If confirmed, delete using:
bun run ${CLAUDE_PLUGIN_ROOT}/lib/session-store.ts delete-task-list <task-list-id>
Or the user can inspect and delete manually:
ls ~/.claude/tasks/<task-list-id>/
rm -r ~/.claude/tasks/<task-list-id>/