Skip to main content
The Problem: As individual productivity increases (3x–10x), the volume of Pull Requests (PRs) multiplies, creating a bottleneck for human reviewers. The Solution: Shift the AI’s role from just a “coder” to a “reviewer” to act as an automated first line of defense.

The “Living” Rulebook

Teams must codify tribal knowledge into a REVIEW_RULES.md file in the repository root. This turns unwritten preferences into a tangible asset the AI can enforce.

Example REVIEW_RULES.md

Agentic Review Workflows

Use a REVIEW_PROCESS.md to define a step-by-step agentic routine for the AI, such as:
  1. Checking out branches
  2. Triaging issues (P0 to P2)
  3. Summarizing findings before a human looks at the code

Example REVIEW_PROCESS.md


Key Takeaway: Codify tribal knowledge into enforceable rules. AI handles the “tedious nits” so humans can focus on architecture and taste.