What problem does it solve? Legacy codebases accumulate technical debt, but teams struggle to decide where refactoring effort pays off. This Skill analyzes working legacy code, catalogs concrete improvement opportunities, ranks them by real return on investment (hotpath impact, coupling, change frequency) rather than aesthetics, and routes each one to the right specialist — without ever modifying the code itself. ## Core Features & Use Cases - Opportunity Inventory: Scans code and classifies each finding by specialist verb: restructure, modularize, decouple, optimize, simplify, standardize, or prune, recording each as a structured YAML+Markdown artifact. - ROI-Based Prioritization: Ranks opportunities by impact, cost, and risk with confidence levels (green/yellow/red) tied to test coverage, so hotpath code is tackled before cosmetic cleanup. - Context-Organized Registry: Groups all opportunities and transformations under _reversa_refactor/<context>/ folders per feature or module, with generated index views and full audit traceability to specs. - Use Case: A developer inherits a monolithic shipping-cost module that is hard to test. They invoke the Skill, which resolves the context, detects a god class and a dependency cycle, ranks them by ROI, and presents a menu routing each finding to /reversa-restructure or /reversa-decouple for gated, reversible transformation. ## Quick Start Ask the agent to analyze the legacy code in a specific module and list which refactorings are worth doing, using the reversa-refactor workflow.
