refactor

Automate AST-aware TypeScript refactors with plan-driven verification workflows.

1.7k|91|Updated Feb 13, 2025
One-click install
npx skills add https://github.com/flowglad/flowglad --skill refactor-flowglad
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: refactor
Source: https://github.com/flowglad/flowglad/tree/main/.claude/skills/refactor
Command: npx skills add https://github.com/flowglad/flowglad --skill refactor-flowglad

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Large-scale refactors across a TypeScript codebase are error-prone and time-consuming, often causing regressions and missed references.

Core Features & Use Cases

  • AST-aware search and replace to safely rename symbols across files
  • Structured, plan-driven workflows (gameplan) for complex migrations
  • Integrated guidance on complexity, tooling choices, and verification steps

Quick Start

Initiate a project-wide rename using an AST-based approach and verify changes with a test run.

Frequently Asked Questions about refactor

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

FAQPage Schema
How do I automate large-scale TypeScript refactors across multiple files?

Large-scale TypeScript refactors are automated using AST-aware search and replace, structured workflows, and validation checks to safely migrate APIs and rename symbols across multiple files.

What is the best way to safely rename symbols across a TypeScript codebase?

The best way to safely rename symbols across a TypeScript codebase is using AST-aware tooling that searches and replaces code structurally, avoiding error-prone manual text replacements.

Can I execute API migrations and signature changes without causing regressions?

Yes, you can execute API migrations and signature changes without regressions by using a plan-driven workflow with integrated verification steps to validate code before shipping.

How do I verify code changes after a codebase-wide migration?

You verify code changes after a codebase-wide migration by running validation checks and test runs as part of a structured gameplan workflow before shipping the final code.

When do I need AST-aware tooling for code migration?

You need AST-aware tooling for code migration when performing complex symbol renames or API signature changes across many files where simple text search and replace risks missing references.

Why do large TypeScript refactors require a plan-driven workflow?

Large TypeScript refactors require a plan-driven workflow to assess complexity, select appropriate tooling, and verify changes systematically, thereby reducing the risk of regressions and missed references.