py-reviewlisted

# Python Review Router Use this skill first for Python code review. Orient on context, then load only the focused skills that match the changed code. ## Before Reviewing: Orient 1. Check Python version from `pyproject.toml`, `setup.cfg`, `tox.ini`, CI, or README. - If `>=3.10`: load all relevant core skills, but apply each rule only when its Python/tool caveat matches. - If `3.8-3.9`: skip syntax rules requiring `>=3.10`. - If unknown: assume minimum 3.10, but phrase version-sensitive findings conservatively. 2. Classify project maturity. - Active/greenfield: full rule set is appropriate. - Mature legacy/maintenance-only: prioritize CRITICAL and HIGH findings. - Automation/scripts: prioritize safety, correctness, resource handling, and clear errors. 3. Check toolchain. - If the project uses `pyright`, do not recommend `mypy`-specific config. - If the project uses `ruff`, defer style/import findings to its configuration. - If no tool is configured, make tool suggestions low-severity unless the issue is correctness-related. 4. Read the exact changed files before flagging issues. - For an uncommitted review, inspect `git status --short`, the unstaged diff, the staged diff (`git diff --cached`), and every relevant untracked file. Plain `git diff` omits untracked files. - Before treating a failed command as a code finding, separate repository behavior from reviewer-environment limits such as sandbox permissions, unavailabl