Specter
A published npm CLI that talks about your codebase in first person. The repo has 73 commands (hotspots, bus factor, dead code, why a file exists), 14 MCP tools so an AI assistant can query the repo, and 19 personality modes such as mentor, critic and noir.
- Role
- Creator
- Years
- 2026
- Status
- Live
specter
- specter scan && specter nextIndex the repo, pick what to look at
- specter hotspotsComplexity x churn = refactoring priority
- specter bus-factorWho leaves = what breaks
- specter why src/utils/api.tsGit history, patterns, context
73 commands, 14 MCP tools, 19 personalities
Numbers
- CLI Commands
- 73
- MCP Tools
- 14
- Personality Modes
- 19
- Automated tests
- 416
See it work
Real output, captured from the product. Open Inspect to see how it got there.
Specter
Code health CLI
specter scan
31 files · 7,235 lines · 183 nodes · 178 edges · 4.7s
specter hotspots
| File | Complexity | Churn | Score |
|---|---|---|---|
| src/ | 100 | 100 | 100 critical |
| src/ | 94 | 97 | 95 critical |
| src/ | 81 | 97 | 89 critical |
Top 3 of 20 · 13 critical, 7 high
The brief
Complexity and churn numbers do not say who owns the risky code or why it exists.
The build
Specter builds a knowledge graph of the repo from the source and its git history. The commands read from that graph, and the MCP server gives an AI assistant the same data.
What shipped
On npm as @purplegumdropz/specter. Release 1.1.1 is published, and main now has 73 commands.