Agent skill · operations · wshobson
review-agent-setup
Configure human-in-the-loop gating for AI agent review actions in Claude Code. Use when setting up a project where an agent may post PR reviews, comments, merges, or edit CI configuration, and you want a cryptographically auditable approval trail with Cedar-enforced gates.
Why this skill is useful
Adds specific commands and workflows for implementing human-in-the-loop approval processes in AI agent actions, which are not commonly found in general documentation.
What it needs
Requires claude installed locally. About 3k tokens when loaded. Last updated 2026-08-05. 38,570 stars on the source repository.
What this skill does
review-agent-governance — Setup Gate AI agent review actions (PR reviews, comments, merges, CI edits) behind explicit human approval. Every attempt, approved or denied, produces an Ed25519-signed receipt. When to use this plugin Install it in projects where a Claude Code agent: Reviews, comments on, or merges pull requests (gh pr review, gh pr merge) Triages issues (gh issue comment, gh issue close) Publishes releases (gh release create) Modifies CI configuration (.github/workflows/, .gitlab-ci.yml) Pushes to protected branches (main, master, release, production) Posts to external notification surfaces (Slack webhooks, Discord) If the agent is only doing local file edits and running tests, this plugin is overkill. Use protect-mcp for general tool-call policy enforcement and skip this one. One-time setup 1. Install the plugin 2. Copy the default policy to your project You can edit this file to match your project's specific rules. See ../agents/review-policy-author.md for guidance on authoring review policies. 3. Create a receipts directory and sign key The first invocation of protect-mcp sign will create the key. Commit the public key from the first receipt so auditors can verify later. Per-session workflow The Cedar policy denies review-surface actions unconditionally. To approve a specific action, open an approval window before it and close it after. Flag file (simplest) Slash command (from within Claude Code) This creates ./.review-approved with the given reason embedded as a note, and writes a human-approved receipt to the chain. A follow-up rm is still needed to close the window. Dry-run everything (force full policy evaluation) If you want every tool call to go through Cedar with no approval bypass: Any tool call matching a forbid rule will be denied; approved windows have no effect. Useful for CI or for a locked-down audit run. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills wshobson/review-agent-setup