prism-refactor-scout

Analyze module complexity, interface usage, and code duplication to generate refactor plans.

Updated May 2, 2026

Search Tags:#refactoring #software quality #codebase analysis #developer productivity #code optimization

Ready to run

npx skills add https://github.com/HunterMcGrew/PRISM --skill prism-refactor-scout

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: prism-refactor-scout
Source: https://github.com/HunterMcGrew/PRISM/tree/main/.cursor/skills/prism-refactor-scout
Command: npx skills add https://github.com/HunterMcGrew/PRISM --skill prism-refactor-scout

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The skill solves the problem of identifying and planning refactor candidates within a codebase, improving its overall structure and maintainability.

Core Features & Use Cases

Refactor Candidate Identification: Scans the codebase for modules that may benefit from refactoring.
Ranking and Grill Passes: Analyzes each candidate and applies a series of passes to assess its potential impact.
Refactor Plan Generation: Outputs a detailed plan for refactoring at .prism/plans/refactor-<slug>.md.

Quick Start

To start a refactor scout session, run: Ren — refactor scout. Where should we start scouting — repo root, or a specific subtree?

Frequently Asked Questions about prism-refactor-scout

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I identify refactor candidates in a complex codebase?▼

Refactor candidates are identified by analyzing module complexity, interface usage, and code duplication. The tool scans the codebase, applies ranking passes to assess potential impact, and outputs a structured refactor plan.

What's the best way to plan codebase refactoring for improved maintainability?▼

Planning codebase refactoring involves generating a detailed refactor plan at `.prism/plans/refactor-<slug>.md`. This plan is derived from analyzing module complexity and code duplication to enhance overall codebase structure.

Do I need Git to analyze codebase complexity and duplication?▼

Yes, Git is required to provide code context for analyzing codebase complexity and duplication. Local storage is also needed to maintain state during the refactor candidate identification process.

How do I start a refactoring session to scan for code optimization opportunities?▼

To start a refactoring session, initiate the refactor scout and specify a starting point, such as the repository root or a specific subtree. The scout will then scan the target area for code optimization opportunities.

Can I target a specific directory subtree for codebase analysis instead of the whole repo?▼

Yes, you can target a specific directory subtree for codebase analysis. When starting the session, you can specify a particular subtree instead of the repository root to focus the refactor candidate identification.

What limitations exist when scanning large codebases for module complexity?▼

Scanning large codebases for module complexity requires Git for code context and local storage for state management. The analysis focuses solely on module complexity, interface usage, and code duplication to generate the refactor plan.