improve-code-quality

To refactor untested legacy code safely, you need a safety net of characterization tests to pin existing behavior before making changes. This skill guides you through creating those tests first, ensuring no current functionality breaks during architectural hardening and cleanup.

Transitioning a prototype to production-ready code requires a structured path of automated testing, dependency management, and system design documentation. This skill orchestrates a multi-phase, resumable workflow that hardens prototypes into robust systems without losing prior decisions.

Characterization testing for existing prototypes works by capturing and pinning the current actual behavior of the code before any refactoring begins. This skill automates the guidance for building these safety nets, ensuring your system's existing logic remains verifiable during reliability engineering.

Yes, you can resume an architectural hardening workflow if you stop halfway. This skill tracks progress across nine distinct phases, from basic testing to advanced system design, ensuring no decision or progress is lost when you pause and return to the reliability engineering task.

Yes, this code quality improvement approach works for dependency management by satisfying specific production-readiness requirements. The structured, decision-based methodology integrates dependency management into its multi-phase workflow alongside automated testing and system design documentation.

You should not use an automated refactoring workflow if your project is still in the early, exploratory prototyping phase where behavior is expected to change rapidly. This skill is designed for hardening existing working prototypes that you are afraid to modify, not for greenfield ideation.