Python Quality Audit

Audit Python without modifying the target. Fan out independent evidence gathering, then synthesize one deduplicated report whose findings can be verified and actioned.

Load python-engineering:standards-for-python-development first. Its shared rules define the preferred Python engineering defaults and repository-precedence rules.

Resolve scope

Interpret the argument as exactly one review surface:

• PR: changed Python files plus affected callers/consumers, tests, docs, config, manifests, generated artifacts, and public contracts.
• diff: the supplied/base diff plus the same affected surface.
• staged: git diff --cached.
• unstaged: git diff plus relevant untracked Python files.
• file/directory: the selected Python target plus materially affected consumers/contracts.

Do not silently broaden into unrelated cleanup. Trace outward far enough to determine whether a finding is local or systemic.

Record the repository's actual Python floor. If the user explicitly supplies a target floor (for example Python 3.15), assess modernization against that target as PROPOSED unless repository configuration already establishes it. Do not recommend syntax or APIs unavailable at the authoritative floor.