SkillsAdd

mksglu/context-mode

ctx-purge

Purge the context-mode knowledge base. Permanently deletes all indexed content and resets session stats. This is destructive and cannot be undone.

All-time #8805 First seen Apr 6, 2026
8-week activity · all time api

Installation

$ npx skills add mksglu/context-mode --skill ctx-purge
View on skills.sh ↗ GitHub repository ↗

Also in this package

Other skills from mksglu/context-mode · top by installs.

npx skills add mksglu/context-mode
context-mode 2.3K ctx-stats 1.4K context-mode-ops 1.3K ctx-doctor 1.2K ctx-upgrade 1.2K ctx-insight 1.1K ctx-index 777 ctx-search 7 improve-codebase-architecture 53 diagnose 53

Browse all from mksglu/context-mode

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 21.3K
License LICENSE
Default branch main
Open issues 120
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,698 B
  • docs SUMMARY.md 196 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1,200 installs

SKILL.md

Context Mode Purge

Permanently deletes session data for this project. Two scopes are supported (issue #520):

  • Project scope (scope: "project"): wipes EVERYTHING — knowledge base, all session DB rows for every session, events markdown, and stats.
  • Session scope (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.

Instructions

  1. Decide the scope first with the user:

- "Wipe just one session?" → ask for the sessionId. - "Wipe the whole project?" → confirm scope:'project' (this is the destructive, irreversible default).

  1. Warn the user about scope:'project'. Everything will be deleted:

- FTS5 knowledge base (all indexed content from ctxindex, ctxfetchandindex, ctxbatchexecute) - Session events DB (analytics, metadata, resume snapshots) for ALL sessions in the project - Session events markdown file - In-memory session stats + persisted stats file

  1. Call the mcpcontext-modectx_purge MCP tool with the chosen parameters:

- Scoped: { confirm: true, sessionId: "<id>" } — implies scope:'session'. - Project: { confirm: true, scope: "project" } — explicit destructive form. - Bare { confirm: true } still works but emits a deprecation warning. Prefer the explicit forms.

  1. Report the result to the user — the response lists exactly what was deleted and (for scoped purges) confirms that other sessions and project stats were preserved.

Schema rules

  • 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.

When to Use

  • Scoped (per-session): scratch acceptance scenarios, drill replays, isolating a polluted session without losing the main working session's stats.
  • Project: KB contains stale or incorrect content polluting search results, switching between unrelated projects in the same session, completely fresh start.

Important

  • 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.
  • There is no undo. Re-index content if you need it again.