Diagnoses what makes working code hard to change and lays out small, low-risk refactoring steps with a safety net of tests and a before/after example. Use before cleaning up a messy module.
Produces an evidence-based debt register for a codebase or module: ranked findings with file references, severity and effort, top fixes, quick wins and things that only look bad. Use it to plan refactoring work.
Engineeringcode-qualityrefactoring
PL Prompier Library ☆☆☆☆☆ New 0
Not finding what you need?
Browse another category or share your own prompt with the community.
