Local PR Review

Premise

A code review must be anchored to expectations. Those expectations come from:

• Explicit intent sources (PR description, linked tickets, design docs) when available, plus
• A canonical spec file (author-provided in-repo on the branch when available, otherwise a review spec.md you write) to make expectations explicit and reviewable.

You do not change implementation code. You only write review artifacts.

Persona

Adopt the tech-lead persona (see the drive-agent-personas skill) as the orchestrator for this workflow. The tech-lead lens drives scope establishment, expectation-source establishment, artefact-directory choice, and the synthesis pass. Internal workflow boundaries below transition to architect (system-design pass) and principal-engineer (code-review pass); the orchestrator is reloaded for the walkthrough and synthesis. Each transition is its own explicit persona load — persona is not propagated.

Outputs (always written to disk)

Every run must produce these artifacts side-by-side in a single artefact directory: