Save 60-80% tokens when AI reads code — MCP server for token-efficient code navigation with AST-aware structural reading
Agent
PROACTIVELY use this when the user asks "what changed in our public API", "did we break anyone", "is this a breaking release", or is about to cut a version. Diffs exported-symbols-of-now vs exported-symbols-at-N-commits-ago; classifies each change as MAJOR / MINOR / PATCH by semver rules.
Agent
Use this when the user asks for a security / quality audit, pre-release sweep, or "scan this for issues". Finds hardcoded secrets, injection shapes, unsafe casts, stale TODOs — classified Critical / Important / Minor. Read-only, NEVER edits, never quotes secrets in output.
Agent
PROACTIVELY use this when the user is about to commit a NON-TRIVIAL change (new feature, fix, refactor) and asks "write a commit message". Reads staged diff, verifies tests pass, drafts Conventional Commit. Refuses mixed diffs (asks to split), failing tests, or empty stage. Do NOT use for docs-only, whitespace-only…
Agent
PROACTIVELY use this when the user says "setup this project for AI-assisted coding", "agent is producing wrong patterns", "new session keeps hallucinating APIs", or asks how to structure CLAUDE.md / AGENTS.md / rules files. Audits the current context setup, proposes improvements, and writes the rules file. Do NOT use…
Agent
Use this when the user asks to find or remove dead / unused code ("clean up this file", "find unused exports", "pre-release cleanup"). Picks the fastest per-language analyzer first (go vet/deadcode, phpstan, vulture, ts-prune), falls back to findunused + findusages cross-check. Output-only — NEVER deletes code itself.
Agent
PROACTIVELY use this when the user reports a bug, stack trace, error message, failing behaviour, or asks "why does X break / fail / throw". Traces root cause via call-tree without reading whole files first. Do NOT use for writing new features or planning changes.
Agent
PROACTIVELY use this when the user asks "which dependencies should I update", "any stale / risky packages", "audit our deps". Combines outdated check with actual in-code usage — stale-and-heavily-used packages are prioritised, stale-and-unused ones flagged for removal.
Agent
PROACTIVELY use this when the user asks to document a decision, write an ADR, add API docs, update README, or says "document this". Writes the WHY (context, constraints, trade-offs), not the WHAT — the diff shows the what. Do NOT use for inline code comments or changelog entries (that's tp-commit-writer).
Agent
PROACTIVELY use this when the user asks "why is this like this", "when was X added / changed", "who added Y", "what was the reason for this code". Returns the minimum commit chain that explains current state — no theorising beyond what commit messages say.
Agent
PROACTIVELY use this when the user asks "what will break if I change X", "who depends on this", or is about to modify a shared symbol / public API / widely-used function. Produces a blast-radius map of affected call sites. Does NOT propose fixes.
Agent
PROACTIVELY use this when the user reports a production incident and asks "what changed before this", "what was deployed in the window", "correlate the bug with recent commits". Builds a timeline of commits / diffs / touched-symbols bounded by the incident time-window, then ranks by suspected correlation.
Agent
PROACTIVELY use this when the user starts implementing a multi-file feature from a task breakdown, or says "build X" / "implement Y" with more than one file involved. Executes in thin vertical slices with test-pass between each. Do NOT use for single-function changes, docs, or config tweaks.
Agent
PROACTIVELY use this BEFORE the user starts any migration — replacing an API, upgrading a framework version, removing a deprecated symbol, switching libraries. Enumerates touch-points as an effort-classified checklist. Do NOT use during the migration itself (file-by-file edits).
Agent
PROACTIVELY use this when the user is exploring an unfamiliar codebase — asks "how is this organised", "what does this project do", "where do I start reading", or starts any conversation in a repo the main agent doesn't know. Orientation map only (layout, entry points, modules); does NOT drill into implementation.
Agent
PROACTIVELY use this when the user reports slow behaviour, asks to profile/optimize, mentions Core Web Vitals / TTFB / response time regressions. Measures FIRST, identifies real bottleneck, proposes targeted fix, never guesses. Do NOT use for general code review or refactoring that isn't perf-driven.
Agent
PROACTIVELY use this when the user asks to review a diff, PR, commit range, or changeset ("review these changes", "look at my PR", "is this safe to merge"). Verdict-first output with Critical / Important findings. Do NOT use for writing code or planning.
Agent
PROACTIVELY use this when the user asks to "plan", "design", or "scope" a refactor, or says "I want to refactor X but need a plan first". Produces step-by-step plan with exact edit context; never applies changes itself.
Agent
PROACTIVELY use this when the user asks "will this PR break production", "what's the blast radius of these changes", or is about to merge into a main branch. Combines diff analysis with dependent discovery — flags risky public-API changes BEFORE they land.
Agent
PROACTIVELY use this general-purpose token-pilot workhorse for ANY coding task (read / edit / search / explore) when no other tp- specialist matches. Prefer token-pilot MCP tools over raw Read / Grep / git. Invoke when the user asks to touch code and no more specific specialist fits.
Agent
PROACTIVELY use this as the FIRST step after /clear, compaction, or a fresh window when a recent sessionsnapshot exists on disk. Reads snapshot + git status + saved docs, returns a ≤200-token briefing. Do NOT use mid-task.
Agent
PROACTIVELY use this before a production release — "prepare to ship", "pre-launch check", "rollout plan needed". Runs the pre-launch checklist, plans staged rollout, defines rollback. Do NOT use for day-to-day deploys of a trusted pipeline (they should pass the checklist automatically).
Agent
PROACTIVELY use this before starting a new feature, project, or change that touches multiple files when no spec exists yet. Writes a structured spec, surfaces assumptions BEFORE any code, produces acceptance criteria. Do NOT use for typo fixes, single-line changes, or unambiguous small tasks.
Agent
PROACTIVELY use this when the user asks "what's untested", "find coverage gaps", "which symbols have zero tests", or wants to plan a testing sprint. Enumerates exported symbols, cross-checks against test-file references, returns a prioritised gap list.
Agent
PROACTIVELY use this when the user reports failing tests, asks to investigate a red CI, or says "these tests are broken / flaky". Identifies root cause and suggests minimal fix — no speculation. Do NOT use to write new tests (that's tp-test-writer).