autonomous-review
This skill uses Claude hooks which can execute code automatically in response to events. Review carefully before installing.
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 driveschp_approve/chp_merge/chp_mergeableprovider seams instead of thegh pr *verbs. When your prompt is running underCODE_HOST=gitlab, treat everygh pr …/gh issue …example as a placeholder for the wrapper-supplied seam — do not hand-rollglabcalls 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).
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 implementation → use autonomous-dev Step 8 (pr-review) |
Dispatcher handed off a PR labeled pending-review or reviewing |
Manual partial review of a draft PR → use the pr-review-toolkit agents directly |
| Run E2E verification + check acceptance criteria + resolve merge conflicts | Just check CI status → use gh pr checks directly |
Cross-Platform Notes
This skill works with any IDE/CLI that supports skills. Browser automation steps use Chrome DevTools MCP — ensure your IDE has this MCP server configured for E2E verification.