optimus:simplify

You can identify technical debt by analyzing your codebase against project-specific coding guidelines to find cross-cutting issues like duplicated logic and pattern inconsistencies, then apply a prioritized refactoring plan with automated test verification.

Code refactoring for cross-cutting concerns targets architectural drift and duplicated logic spanning multiple files. It analyzes the entire project against established patterns to suggest simplifications that improve overall clarity and consistency.

Yes, project documentation and a test command are required for full functionality. The documentation defines project-specific coding guidelines, while the test command verifies refactoring changes and automatically reverts any modifications that fail.

Yes, code simplification supports iterative, on-demand application. Changes are applied only after user approval and verified with the project's test suite, automatically rolling back any modifications that fail tests.

You should review for technical debt after adding major features to ensure new code aligns with established patterns. It helps clean up accumulated inconsistencies and duplicated logic across the entire project before they compound.