Plan internal code refactoring while preserving public API signatures.
npx skills add https://github.com/li3p/skills --skill refactor-safe-li3p
Please help me install this Agent Skill. Skill: refactor-safe Source: https://github.com/li3p/skills/tree/main/skills/refactor-safe Command: npx skills add https://github.com/li3p/skills --skill refactor-safe-li3p
Refactor internal implementation without changing public API or behavior. Use when improving structure, readability, duplication, or complexity while preserving exported signatures, return shapes, errors, and tests.
Describe the internal changes you want to make while preserving the public API, and I will guide you through safe, incremental refactoring steps.
High-intent search queries and answers about installing and using this skill.
To refactor internal code without changing the public API, you must preserve exported names, signatures, return shapes, and error messages while isolating changes to private helpers and internal components.
The best way to reduce code duplication while preserving exported signatures is to isolate changes to private helpers, simplify internal branches, and maintain public routes and schemas without introducing new dependencies.
Plan safe structural improvements by describing the internal changes you want, then applying incremental refactoring steps that satisfy constraints to preserve tests, return shapes, and edge-case behavior across modules.
Yes, you can simplify internal branches without breaking existing tests by ensuring error messages and edge-case behavior stay intact, isolating modifications to private helpers rather than exported signatures.
Limitations include avoiding new dependencies and ensuring error messages, config keys, and events stay intact unless explicitly approved, restricting modifications strictly to internal components and private helpers.
You need to preserve return shapes during a code maintenance refactor whenever you are reorganizing internals for readability or complexity reduction across modules, libraries, and tests without changing public behavior.
ResearchMonkeyAnalyze test quality and coverage to identify gaps and flaky tests.
rsmdtPlan staged code refactorings with baseline tests and behavior preservation.
andy4917Analyze TypeScript code for architectural weaknesses, type inconsistencies, and error handling gaps.
linehaul-aiReview and refactor Go code against Effective Go guidelines.
