Pytest Code Review

A structured review process for pytest test files that forces you to work through five gates before flagging issues: scoping which test files you're looking at, identifying async versus sync patterns, checking fixture usage, validating mock and patch locations, and finally documenting specific findings with line numbers. It's opinionated about the order you review things, which is either helpful discipline or annoying process depending on whether you usually skip straight to nitpicking parametrize usage before confirming the async tests are even using AsyncMock correctly. The gate system prevents generic advice and makes you cite actual file paths and test node IDs. Best when you're reviewing pull requests with test changes and want to avoid the usual back and forth about whether fixtures are cleaned up or mocks are patched at the call site.