Python Backend Fundamentals Review

Python version mismatches, blocking async code, and unclear error handling can turn routine backend changes into production problems. Get a prioritized review with file-specific findings, practical fixes, and suggested tests.

What it does

• Checks version compatibility: Compares Python requirements with deployment, CI, dependencies, and tooling.
• Finds correctness risks: Reviews async behavior, exceptions, configuration, and resource cleanup.
• Improves maintainability: Examines typing, readability, imports, logging, and test coverage.
• Prioritizes useful changes: Separates correctness risks from cleanup and optional modernization.
• Guides verification: Recommends targeted tests and small, reviewable improvements.

How it works

1. Share your Python backend repository and target Python version, if known.
2. Choose whether to allow web research, a saved project baseline, or code changes.
3. Receive a review with locations, risks, recommendations, and a staged improvement plan.
4. Use the suggested follow-up requests to tackle individual findings.

Works with

Python backend repositories, including project configuration, Dockerfiles, CI settings, dependency files, and tests. It can assess existing mypy, pyright, and Ruff settings where configured.

Why use this skill

You get concrete issues to investigate rather than a generic clean-code checklist. Recommendations account for existing project conventions and the cost of changing working code, helping avoid unnecessary rewrites.

Use cases

• Check readiness for a Python version upgrade.
• Investigate blocking work in async request paths.
• Resolve differences between local, CI, and production settings.
• Plan small typing and test improvements.

Known limitations

Focused on Python fundamentals, not full architecture, framework, security, or performance audits. Reviews leave code unchanged unless edits are explicitly allowed.