What problem does it solve? Teams planning a cleanup sprint or paying down technical debt often lack an objective, evidence-based view of where the real structural problems are. This Skill performs a read-only, whole-project structural audit and distills architecture, hotspots, dependency tangles, and dead code into a numbered findings register with severity, effort, and file:line evidence. ## Core Features & Use Cases - Architecture mapping and hotspot analysis: Builds a compact architecture map, then crosses git churn with file size to find the files most worth refactoring. - Delegated deep read: Launches a read-only subagent to verify dependency cycles, layering violations, god modules, and dead-code candidates, with every claim spot-checked against cited locations. - Numbered findings register: Writes a report to .marvin/refactor/NNN-audit-<slug>.md with severity and effort per finding, and offers to file findings as board chores via the task MCP tool. - Use Case: Before planning a cleanup sprint, ask for a refactoring audit of the repository to get a ranked register of structural issues — for example, a 1,800-line module changed 47 times in a year and imported by 23 files — each with evidence and a suggested direction. ## Quick Start Ask Claude to run a refactoring audit of this codebase and report the top structural hotspots and tech-debt findings.
