Analyzing Codebases
Runs real static-analysis tooling and ranks refactor hotspots by churn x complexity.
Funktioniert mit Setup
Was es kann
Detects a project's languages and monorepo shape, runs the matching static-analysis toolchain (dependency graph, duplication, cognitive complexity, semantic patterns), and writes a machine-parseable refactor map ranking the top 20 hotspots by git churn times complexity. Triggers on /aref or an explicit ask to analyze a codebase before refactoring.
Testbericht
Ran the real toolchain on a throwaway TS repo: jscpd correctly caught an exact-clone duplication cluster and git-churn math correctly ranked the touched-and-duplicated file above its untouched twin (score 96 vs 16, both cognitive complexity 16). But the reference doc's literal commands for dependency-cruiser and eslint-plugin-sonarjs both failed out of the box (needed --no-config plus --include-only, and a manually added @typescript-eslint/parser) — friction not mentioned anywhere in the skill.
Getestet am: 2026-07-15 · Claude Code 2.x (agent harness)
Installation
git clone https://github.com/wayne930242/Reflexive-Claude-Code mkdir -p ~/.claude/skills cp -r Reflexive-Claude-Code/plugins/aref/skills/analyzing-codebases ~/.claude/skills/analyzing-codebases
Befehle & Beispiel-Prompts
/analyzing-codebasesRuns real static-analysis tooling and ranks refactor hotspots by churn x complexity.
Skills reagieren auf normale Anfragen — keine Slash-Befehle nötig. Nach der Installation aktivieren Prompts wie diese den Skill (auf Englisch):
Analyze this codebase and tell me what needs refactoring firstGive me a hotspot map of the messiest, most complex files before we refactorWhich files here have the highest git churn combined with high complexity?