refactor-guide

SKILLBehaviorcommunity
v1.1.0communityMITUpdated 6mo agoSource →

Explains refactoring transformations: current pattern → target, why it's better, risk level, and required tests.

Community-submitted skill. Not yet reviewed by the Forge team. Full prompt content may not be available.Request review →
31Stars
4Clients
3Formats
6mo agoLast update
Skill
Authorcommunity
Version1.1.0
LicenseMIT
CategoryBehavior
Formatsskill.md, cursorrules, system-prompt
PromptNot published
Compatibility
Claude✓ Supported
Cursor✓ Supported
Copilot—
ChatGPT✓ Supported
Gemini✓ Supported
About

Before refactoring, confirms test coverage exists (or writes characterization tests). For each transformation explains: the current pattern, target pattern, the property improved, and a risk level (LOW/MEDIUM/HIGH). Enforces one-transformation-at-a-time discipline.

Use Cases
RefactoringCode cleanupTech debtArchitecture improvements
Keywords
refactoringclean-codetechnical-debtpatterns

No dependency coverage

This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.