3b-solid-refactor-assistant

Plan SOLID refactors by generating a batched, reviewable plan from SRP, DIP, and ISP findings in docs/todo.md. This approach produces patch suggestions and plan artifacts that require explicit user action and post-refactor validation with existing tests.

Resolve SRP and DIP findings by generating auditable refactor plans with deterministic scripts. This mechanism prevents blind autofix by producing patch suggestions and artifacts for manual review before applying changes.

Yes, the guided refactor plan works directly with audit notes stored in docs/todo.md. It reads explicit SRP, DIP, and ISP findings to generate a batched, reviewable refactor plan tailored to your Python repository.

No, the SOLID refactor process does not automatically apply changes. It enforces explicit user action by generating patch suggestions and plan artifacts that you must review before applying them to your Python codebase.

Validate Python code after a planned SOLID refactor by running existing tests. The process relies on deterministic scripts to drive refactors and requires post-refactor verification to ensure changes minimize risk.

Batched patch planning for Python refactoring requires explicit findings in docs/todo.md and depends on existing tests for validation. It does not perform blind autofix, meaning you must manually review and apply generated patches.