instaget-backend-refactoring-assistant

Multi-module refactoring requires automated dependency analysis to update all usages across dependent modules. This skill analyzes the impact of signature changes or renames, applies updates across common and infrastructure modules, and ensures compilation and tests run successfully.

Multi-module refactoring validates changes by compiling the project and running tests to ensure no dependent modules break. It also enforces team coding standards by adhering to the project's conventions defined in .docs/conventions/code-convention.md and documents all modifications.

Yes, automated refactoring is designed for large codebases organized in common and infrastructure modules. It streamlines safe changes by analyzing cross-module dependencies, enforcing conventions, and verifying that builds and tests pass after updates.

The best way to enforce code conventions during multi-module refactoring is to automate compliance checks against documented standards. This skill adheres to rules in .docs/conventions/code-convention.md while applying signature changes, improving code quality, and documenting updates.

Refactoring large multi-module projects fails without impact analysis because renaming methods or changing signatures breaks dependent modules. Automated dependency analysis prevents errors by updating all usages, verifying builds, and running tests across the entire codebase.