backend-code-review

Review Python backend code by applying a structured checklist covering architecture, security, performance, testing, and observability to generate actionable fixes and refactoring snippets for improved maintainability.

Yes, you can audit pending changes in a Python backend module. The review process detects the evaluation mode and targets pending changes, code snippets, or file-wide assessments under the src/backend/ directory.

The best way to get actionable fixes for backend code quality issues is through a checklist-driven evaluation that returns concrete refactors and example code snippets directly applicable to your codebase.

No, this code review process does not work with frontend code. It is strictly designed to audit Python files located under the src/backend/ directory and should not be used for src/frontend/ evaluations.

To start a backend code review, inspect the backend code, indicate the scope of the review, and provide the target Python files or code snippets to begin the checklist-driven evaluation.