cxpak
Structured codebase context for Claude. Auto-context on every prompt plus an on-demand single-page dashboard with Cmd+K command palette: three modes — Overview (health, top risks, signals, repo-DNA), Explore (dependency + risk lenses), and History (architecture timeline). 5 intent-parameterized MCP tools, 12 HTTP endpoints, 14 LSP custom methods — all wired to real intelligence: health scoring, blast radius, change prediction, drift detection, security surface, data flow tracing, cross-language resolution. tree-sitter across 44 languages. Cross-process deterministic output.
Plugin cxpak from marketplace cxpak-marketplace in Barnett-Studios/cxpak. Commands read from the repo's manifest — 19 days ago.
This plugin runs code on your machine — it starts local MCP servers. The exact commands are listed below; read them before installing.
What it installs
Skills (3)
codebase-contextUse when the user asks about codebase structure, architecture, what a project does, how components relate, or needs project-wide context to answer a question.
diff-contextUse when the user asks to review changes, understand what changed, prepare a PR description, or needs context about recent modifications.
setupSet up the cxpak MCP server for the current project. Use when the user wants to enable cxpak tools or when cxpak MCP is not connected.
Slash commands (4)
/cxpak:cleanClear the cxpak cache and output files
/cxpak:diffRun cxpak diff to show changes with dependency context within a token budget
/cxpak:overviewRun cxpak overview to get structured codebase context within a token budget
/cxpak:traceRun cxpak trace to find a symbol and pack relevant code paths within a token budget
MCP servers (1)
cxpakruns: ${CLAUDE_PLUGIN_ROOT}/lib/ensure-cxpak-serve
Maintain cxpak?
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.