Code review
Analyze code changes for impact, quality, and safety using CodeLens MCP toolsFrom its SKILL.md
npx -y skills add mupozg823/codelens-mcp-plugin --skill code-reviewAssembled 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.2 KB, as published. Nobody here has run it
CodeLens Code Review
Analyze the impact and safety of code changes using structural analysis.
Workflow
- Identify changes: Call
get_changed_fileswith the target ref (default: HEAD~1) - Assess impact: For each changed file, call
graphwith mode=impact to find affected downstream files - Check references: For modified symbols, call
find_referencing_symbolsto find callers that may break - Run diagnostics: Call
get_file_diagnosticson changed files to detect type errors or warnings - Summarize: Report the blast radius, breaking changes risk, and diagnostic issues
Usage
/codelens-review # Review HEAD~1 changes
/codelens-review main # Review changes vs main branch
Output Format
For each changed file, report:
- File path and change status (M/A/D)
- Symbol count and types affected
- Blast radius (number of downstream files)
- Diagnostic issues (errors/warnings)
- Risk assessment (low/medium/high)