skills/ctx-purge/SKILL.md
Purge the context-mode knowledge base. Permanently deletes all indexed content and resets session stats. This is destructive and cannot be undone. Trigger: /context-mode:ctx-purge
npx skillsauth add mksglu/claude-context-mode ctx-purgeInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Permanently deletes session data for this project. Two scopes are supported (issue #520):
scope: "project"): wipes EVERYTHING — knowledge base, all session DB rows for every session, events markdown, and stats.sessionId: "<id>" or scope: "session"): wipes ONLY the matching session's rows + FTS5 chunks. Sibling sessions, project stats, and the FTS5 store file are preserved.sessionId.ctx_index, ctx_fetch_and_index, ctx_batch_execute)mcp__context-mode__ctx_purge MCP tool with the chosen parameters:
{ confirm: true, sessionId: "<id>" } — implies scope:'session'.{ confirm: true, scope: "project" } — explicit destructive form.{ confirm: true } still works but emits a deprecation warning. Prefer the explicit forms.confirm: true is always required.sessionId and scope: "project" together is REJECTED as ambiguous (the sessionId implies session scope; combining with project scope contradicts intent).scope: "session" without sessionId throws — sessionId is required.ctx_purge is the only way to delete session data. No other mechanism exists.ctx_stats is read-only — shows statistics only./clear and /compact do NOT affect any context-mode data.documentation
Search context-mode's persistent FTS5 knowledge base for previously indexed local project content, documentation, or session memory. Trigger: /context-mode:ctx-search
tools
Index a local file or directory into context-mode's persistent FTS5 knowledge base so future ctx_search calls can retrieve focused snippets without rereading raw files. Trigger: /context-mode:ctx-index
tools
Use context-mode tools (ctx_execute, ctx_execute_file) instead of Bash/cat when processing large outputs. Triggers: "analyze logs", "summarize output", "process data", "parse JSON", "filter results", "extract errors", "check build output", "analyze dependencies", "process API response", "large file analysis", "page snapshot", "browser snapshot", "DOM structure", "inspect page", "accessibility tree", "Playwright snapshot", "run tests", "test output", "coverage report", "git log", "recent commits", "diff between branches", "list containers", "pod status", "disk usage", "fetch docs", "API reference", "index documentation", "call API", "check response", "query results", "find TODOs", "count lines", "codebase statistics", "security audit", "outdated packages", "dependency tree", "cloud resources", "CI/CD output". Also triggers on ANY MCP tool output that may exceed 20 lines. Subagent routing is handled automatically via PreToolUse hook.
development
Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.