refactor-scout

Name: refactor-scout
Availability: InStock
Author: hoonzi

Identify structural improvement opportunities in a codebase and log them to REFACTOR_BACKLOG.md.

Updated Jan 26, 2026

Search Tags:#architecture #structure #refactor #backlog #code-quality #identify #scout

Ready to run

npx skills add https://github.com/hoonzinope/skills --skill refactor-scout

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Identify opportunities to improve code structure and maintainability without altering source code, and record them in a centralized backlog.

Core Features & Use Cases

Identify modules with ambiguous boundaries, duplicated logic, and high cohesion/low coupling opportunities to improve architecture without changing behavior.
Log concrete refactor backlog entries (RF IDs) in .documents/review/REFACTOR_BACKLOG.md for future planning and traceability.
Use during codebase maintenance to plan structural improvements during sprints or architectural reviews.

Quick Start

Ask the agent to scan the repository and generate a dated refactor backlog entry into .documents/review/REFACTOR_BACKLOG.md.

Frequently Asked Questions about refactor-scout

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

FAQPage Schema

How do I identify structural refactoring opportunities without changing source code?▼

To identify structural refactoring opportunities without touching source code, scan the repository for ambiguous module boundaries, duplicated logic, and long functions. The analysis captures results as concrete backlog entries with traceable IDs in a dedicated review markdown file.

What is a code refactor backlog and how does it help with maintenance?▼

A code refactor backlog is a centralized markdown file that logs concrete structural improvement opportunities. It helps during maintenance by recording dated entries with traceable IDs for future sprint planning and architectural reviews without requiring immediate behavioral changes.

How do I detect modules with ambiguous boundaries and duplicated logic across a repository?▼

Detect modules with ambiguous boundaries and duplicated logic by analyzing the repository structure for high cohesion and low coupling opportunities. The scan identifies these architectural issues and logs them into a review markdown file for future planning.

Can I generate a refactor backlog during an architectural review without altering program behavior?▼

Yes, you can generate a dated refactor backlog during architectural reviews without altering program behavior. The process scopes modules, boundaries, duplication, and long functions across the repository, writing exclusively to a designated review markdown file to avoid any behavioral changes.

What's the best way to plan structural code improvements during sprints?▼

The best way to plan structural code improvements during sprints is to scan the repository and generate a dated refactor backlog entry. This approach captures architectural improvements like boundary clarification and duplication removal into a centralized markdown file for traceable sprint planning.

Does running a code structure analysis modify existing source files?▼

Running a code structure analysis does not modify existing source files. The process identifies structural improvement opportunities across the codebase but writes only to a specific review markdown file, ensuring no behavioral changes occur to the source code.