autonomous-reviewlisted

# Autonomous Review Mode > **Provider-lane scope.** The prose below is written in GitHub terms — `gh pr review`, `gh pr merge`, `gh pr checks`, `gh pr view`, `gh issue view` — because those are the GitHub-lane concrete forms. Every INV-52 / INV-44 rule (agent posts a verdict comment; wrapper owns approve/request-changes/merge; wrapper enforces the mergeable hard gate) is provider-agnostic and applies verbatim to the GitLab lane (`CODE_HOST=gitlab`): the wrapper drives `chp_approve` / `chp_merge` / `chp_mergeable` provider seams instead of the `gh pr *` verbs. When your prompt is running under `CODE_HOST=gitlab`, treat every `gh pr …` / `gh issue …` example as a placeholder for the wrapper-supplied seam — do not hand-roll `glab` calls to replace them. Review PRs created by autonomous development sessions thoroughly and objectively, then **post a verdict comment** (`Review PASSED` or `Review findings:`). The review **wrapper** owns the GitHub-native action: it submits `--approve` and merges on a PASS (after its mergeable + `no-auto-close` gates) and submits `--request-changes` on a blocking FAIL. You never run `gh pr review` or `gh pr merge` yourself — see [Who submits the GitHub-native PR action (INV-52)](#who-submits-the-github-native-pr-action-inv-52). ## When to Use | Use this skill | Use a different skill | |---|---| | Final verdict on a completed PR (post the verdict comment; the wrapper approves+merges or requests changes) | In-flight dev-side self-review during impl