Refactor code with impact analysis and stepwise test verification.
npx skills add https://github.com/islee23520/lfg --skill refactor-islee23520
Please help me install this Agent Skill. Skill: refactor Source: https://github.com/islee23520/lfg/tree/main/skills/refactor Command: npx skills add https://github.com/islee23520/lfg --skill refactor-islee23520
This Skill helps you perform targeted code refactors without breaking behavior, by turning vague cleanup goals into a disciplined, test-backed workflow.
Ask the refactor skill to analyze the target code and carry out a safe, test-verified refactoring plan.
High-intent search queries and answers about installing and using this skill.
To safely refactor code across multiple files, you must map dependencies and assess tests before editing. This approach uses disciplined impact analysis and stepwise validation to change implementation while preserving behavior.
The best way to rename symbols across a project involves mapping the target code and its dependencies first. Applying structured planning and test verification reduces regressions during the symbol rename process.
Impact analysis for code modernization works by mapping the target code, its dependencies, and the files most likely to be affected. This identifies potential regressions before any structural extraction or cleanup edit is made.
Yes, test verification requires assessing your current tests to establish a safety net. Continuous verification against these tests ensures your code cleanup or structural extraction preserves the original behavior.
You can split a large service into smaller modules without regressions by using deterministic refactoring steps. This requires codebase mapping and stepwise validation to ensure behavior remains unchanged.
A key limitation of automated code modernization is failing to map dependencies beforehand. Without disciplined impact analysis and continuous test verification, structural changes risk introducing hidden regressions across affected files.
raybirdRename, extract, and split code symbols using GitNexus CLI graph analysis.
outfitter-devRun automated Navigator CLI tests with bun and navigator-server.
cdman28Analyze Python and JavaScript/TypeScript code for smells, complexity, and refactoring opportunities.
TheBushidoCollectiveAdd characterization tests before refactoring untested legacy code.
