Review

Findings-first analysis of a working tree, branch, commit range, or pull request. A generic review runs the production-readiness baseline plus only the specialized lenses the diff warrants. It never asks the user to choose a review template.

Choose execution

For a review associated with a pull request, the first step is to ask exactly:

Publish review on PR?

Skip the question when the user already answered it, explicitly asked for a read-only/draft findings report, or the target has no pull request. The answer selects execution, not review lenses:

Execution	Use when
`findings`	Read-only review; default for non-PR targets or when the user declines publishing
`publish`	Review a PR end to end, reconcile drafts, and submit a friendly GitHub `COMMENT` review
`quality`	Explicit merge-prep execution: audit, boy-scout refactors, tests, and repo gates; changes code

Routing rules: