Pre-PR Review

For a direct invocation, first use shared/references/model-preview.md. Nested calls reuse the parent's selected snapshot without another prompt or unlisted workers.

Check whether a completed implementation is ready for pull request review. Reuse valid task and integration evidence. Run only the work needed to close gaps. The acceptance contract is a scoped, verified local change with no confirmed P0, P1, or P2 finding left open. Approval from a reviewer alone does not meet this contract.

Scope and authority

An explicit request to run this workflow authorizes local simplification, scoped fixes, and verification. Preserve unrelated changes. Keep the result local: do not commit, push, publish comments, open a pull request, merge, or deploy.

Read the task requirements and active project rules. Confirm the intended pull request base branch from the task or repository configuration. Ask only if the target remains ambiguous. Review committed and uncommitted task changes against that base, and pass the same base and requirements to every stage. Do not let a child skill replace the intended base with the repository default.

If no task changes exist, report no-changes and stop before review. An unreadable diff is a blocker, not an empty result.

1. Check existing evidence

Read the available task reports, integration report, residual findings, and referenced review and verification evidence. Inspect the existing run state and approved model plan when present. A report path or completion label alone is not proof of coverage.