refactor-agent

To fix circular dependencies and SOLID violations, you can use an agent that reads local quality reports to detect architectural drift, propose concrete refactors, and apply approved changes. This enforces clean architecture rules like one file per class while preserving behavior.

Architectural drift is gradual structural degradation causing complexity spikes and dependency cycles. You detect it by evaluating local quality reports in .agent/reports to extract findings on complexity (C901) and type-safety issues, which then guide targeted refactoring proposals.

Refactor high C901 complexity warnings by feeding local quality reports into an analysis tool that proposes file or class-level refactors. The agent outlines a clean architecture solution, verifies atomic structure, and runs tests to prevent regressions after applying changes.

Yes, you need local quality reports. The agent requires reports stored in the .agent/reports directory to extract findings on type-safety issues, circular dependencies, and complexity before it can propose and apply safe refactoring changes to your codebase.

Yes, the agent proposes concrete file or class-level refactors and applies changes only after user confirmation. It includes a verification loop to ensure atomic structure, successful tests, and preserved traceability, preventing unreviewed modifications to your codebase.

The best way to resolve type-safety issues without regressions is using a guided agent that verifies behavior after changes. It enforces SOLID principles, checks for atomic structure, and runs tests to ensure successful implementation while preserving traceability.