refactor

Scan codebases for refactoring opportunities and log issues to .claude/ISSUES.md.

12|1|Updated Aug 29, 2025
One-click install
npx skills add https://github.com/Pageloom/weft-id --skill refactor-pageloom
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: refactor
Source: https://github.com/Pageloom/weft-id/tree/main/.claude/skills/refactor
Command: npx skills add https://github.com/Pageloom/weft-id --skill refactor-pageloom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Refactor Agent helps teams uncover refactoring opportunities and technical debt, enabling cleaner, more maintainable code and easier navigation for future changes.

Core Features & Use Cases

  • Identify large, God-like modules and regions with high complexity.
  • Detect duplicated logic and inconsistent patterns to unify design decisions.
  • Generate actionable issues and track history in .claude/ISSUES.md and REFACTOR_HISTORY.md.

Quick Start

Run the Refactor Agent against your codebase to surface top-priority refactoring candidates and document suggested changes.

Frequently Asked Questions about refactor

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

FAQPage Schema
How do I identify technical debt and refactoring opportunities in my codebase?▼

Identify technical debt and refactoring opportunities by scanning the codebase for large God-like modules, duplicated logic, and complex functions, then logging actionable issues and history to .claude/ISSUES.md and .claude/REFACTOR_HISTORY.md for improved maintainability.

What is the best way to detect duplicated logic and inconsistent patterns across multiple languages?▼

Detect duplicated logic and inconsistent patterns across languages by applying the refactoring scanner to typical software artifacts, which surfaces unified design decisions and documents inconsistencies directly in .claude/ISSUES.md.

Can I track refactoring history and document code quality issues automatically?▼

Track refactoring history and document code quality issues automatically by scanning the codebase, logging historical changes, and reporting identified technical debt to .claude/REFACTOR_HISTORY.md and .claude/ISSUES.md.

How do I find God modules and high complexity regions in my architecture?▼

Find God modules and high complexity regions through architecture analysis that scans for large modules and complex functions, generating top-priority refactoring candidates and documenting suggested changes for easier future navigation.

Does this refactoring tool require any specific dependencies or environment setup to run?▼

This refactoring tool requires no specific dependencies or environment setup to run, operating independently to scan software artifacts and output technical debt reports to .claude/ISSUES.md and .claude/REFACTOR_HISTORY.md.

What are the limitations of using automated architecture analysis for technical debt?▼

Automated architecture analysis for technical debt focuses on identifying and documenting opportunities rather than directly modifying code, meaning developers must manually apply the suggested refactoring changes logged in .claude/ISSUES.md.