python-refactor

Analyze the code for duplication and side effects first, then apply minimal safe transformations like extracting functions or splitting files while preserving the public API. Verify with a before/after diff summary and tests confirming behavior is unchanged.

Extract database operations and business rules into a dedicated service class, leaving the view as a thin wrapper that calls the service. For example, move Player.objects.create calls into a PlayerService with typed static or async methods.

Convert only when the surrounding framework and call sites support async, such as Django async views or FastAPI endpoints. Converting without understanding implications can break callers, so preserve existing async/sync patterns by default.

Avoid overengineering simple scripts, adding excessive abstraction, breaking existing APIs without permission, and removing code that seems redundant but serves a purpose. Refactoring should not change behavior unless explicitly requested.

Yes, adding type hints is a standard part of refactoring for clarity and IDE support. Apply them where they improve readability, alongside consistent naming conventions and organized imports following PEP8.