Old Python Code Review

Workflow

1. Apply repo-rules-reader to the requested repo rule files. For the default review baseline, read AGENTS.md, docs/REPO_STYLE.md, docs/PYTHON_STYLE.md, docs/PYTEST_STYLE.md when present, and docs/CHANGELOG.md.
2. Extract the review-relevant rules, especially how to run Python, Python style, pytest style, repo workflow rules, and the latest changelog entry.
3. Inspect changed files first (git diff, git status --short), then inspect related call sites.
4. If the repo has docs/active_plans/, identify the active plan document(s) that govern the change. Otherwise, skip plan-conformance steps.
5. If an active plan exists, map code and tests to plan requirements, acceptance criteria, and stated constraints. Otherwise, skip this step.
6. Prioritize findings by severity: plan mismatch/regressions when applicable, correctness/safety, then maintainability.
7. Provide concrete, minimal fixes with before/after examples when a fix is straightforward.
8. Flag uncertainty explicitly and ask targeted review questions for unclear logic or contracts.