python-refactoring

To refactor Python code without changing behavior, you run a structured workflow that enforces pre-flight checks, requires existing tests to stay green, and applies a fixed catalog of move, extract, inline, and rename operations with disciplined commits.

Moving code into domain folders using hexagonal architecture requires domain-aware refactoring that applies ports and adapters principles, extracting atoms, molecules, ports, and adapters while ensuring tests remain green throughout the process.

Yes, existing tests are required before starting a Python refactoring workflow. The safety-first approach enforces pre-flight checks that demand a green test baseline, ensuring all refactors preserve observable behavior without regressions.

The best way to extract a port or adapter during Python refactoring is to use a structured refactor catalog that supports extract port and extract adapter operations, enforcing disciplined commits and verifying tests stay green after each move.

Yes, you can rename code to match domain language safely in Python projects by using the rename-to-domain refactor operation, which enforces test verification and disciplined commits to preserve observable behavior throughout the change.

Pre-flight checks are necessary before refactoring Python code to verify a green test baseline exists, ensuring the safety-first workflow can detect behavior changes and prevent regressions during move, extract, inline, or rename operations.