refactoring

Detect and remove code smells in TypeScript, JavaScript, and React applications.

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/jey3dayo/apm-workspace --skill refactoring-jey3dayo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: refactoring
Source: https://github.com/jey3dayo/apm-workspace/tree/main/catalog/skills/refactoring
Command: npx skills add https://github.com/jey3dayo/apm-workspace --skill refactoring-jey3dayo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires similarity-ts, react-doctor, tsr, code-quality-improvement, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill addresses the need for an integrated, systematic approach to refactor TypeScript, JavaScript, and React code, helping to maintain code quality and improve organizational structure.

Core Features & Use Cases

  • Diagnostic Analysis: Identifies issues such as duplicate code, boundary ownership, and dead code.
  • Parallel Diagnostics: Executes multiple diagnostics in parallel for faster results.
  • Incremental Refactoring: Provides a three-phase workflow for refactoring (Diagnose -> Analyze & Plan -> Execute).
  • Skill Delegation: Uses specialized skills for specific tasks like duplicate code analysis, ESLint errors, and dead code removal.
  • Use Case: Use this Skill when refactoring a large codebase, focusing on improving code quality and reducing technical debt.

Quick Start

Run the refactoring skill to start the refactoring process on your codebase.

Frequently Asked Questions about refactoring

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

FAQPage Schema
How do I refactor a large TypeScript and React codebase to reduce technical debt?

To refactor a large TypeScript and React codebase, you can use an automated diagnostic workflow that detects code smells like duplicate code and dead code, providing an incremental three-phase refactoring process to systematically reduce technical debt.

What is the best way to detect and remove code smells in JavaScript applications?

The best way to detect and remove code smells in JavaScript applications is through parallel diagnostics that identify duplicate code, boundary ownership issues, and dead code, followed by delegating removal tasks to specialized code quality tools.

How does incremental refactoring work for improving code organization?

Incremental refactoring works by executing a three-phase workflow: diagnose code issues, analyze and plan the restructuring, and execute the changes, ensuring structured improvements to code organization and quality.

Can I run parallel diagnostics to find duplicate code and dead code in React components?

Yes, you can run parallel diagnostics to efficiently find duplicate code and dead code in React components, utilizing specialized dependencies for similarity analysis and dead code removal to accelerate the detection process.

Does automated refactoring support specialized tools for ESLint errors and boundary ownership analysis?

Yes, automated refactoring supports specialized skill delegation for handling specific tasks including ESLint errors, boundary ownership analysis, and dead code removal to ensure comprehensive code quality improvements.

When should I use an automated refactoring workflow instead of manual code cleanup?

You should use an automated refactoring workflow when maintaining a large codebase, as it systematically addresses code quality and organizational structure through parallel diagnostics and incremental execution, which manual cleanup cannot efficiently scale to.