Peer Review

Step 1: Gather context

Read everything relevant before analyzing:

• Requirements: the spec, ticket, or PR description defining what must be built
• Plan: the implementation plan, design doc, or proposed changes
• Code: the actual implementation, diff, or relevant source
• Contracts: OpenAPI/protobuf/API docs; package.json/requirements.txt/Cargo.toml for related libs
• History: related bugs, incidents, or post-mortems
• Tests: existing test files for current coverage

Step 2: Analyze against requirements