Analyze
Deep architecture analysis — dependencies, coupling, dead code, circular importsFrom its SKILL.md
npx -y skills add mupozg823/codelens-mcp-plugin --skill analyzeAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.4 KB, as published. Nobody here has run it
CodeLens Architecture Analysis
Perform a comprehensive architecture health check on the codebase.
Workflow
- Centrality: Call
reviewwith mode=architecture for the structure summary and the PageRank key files (the most coupled ones) - Dead code: Call
reviewwith mode=dead to find unreachable symbols and unused exports - Circular deps: Call
reviewwith mode=boundary to detect import cycles - Hot spots: For the top 5 most important files, call
graphwith mode=impact to assess risk
Every step stays on the CORE-20 default surface (ADR-0016), so each one is callable
as a session's first tool call on any host. review mode=dead / mode=boundary and
graph mode=impact route to the same dead_code_report / module_boundary_report /
impact_report handlers as before. For finer-grained centrality, get_symbol_importance
remains a Full-preset follow-up: expand it with tools/list {"namespace":"graph"} first.
Usage
/codelens-analyze # Full architecture analysis
Output Format
- Dependency graph summary (most connected nodes)
- Dead code candidates with confidence scores
- Circular dependency cycles (if any)
- Risk hot spots (high blast radius + high centrality)
- Actionable recommendations