[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75GAZFS4W871TZT0PE3NMRR":3,"skill-same:01M75GAZFS4W871TZT0PE3NMRR":44},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M75GAZFS4W871TZT0PE3NMRR","review-agent-setup",null,"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.","RudyCity\u002Fsuperagent","RudyCity","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F82188919?v=4","01M75FP5X8AW8ACBH0SH34WS7M","01M75FP5YAHJK8M1Q52BWXB82K",70,"MIT","https:\u002F\u002Fgithub.com\u002FRudyCity\u002Fsuperagent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Freview-agent-setup\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: review-agent-setup\ndescription: 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.\n---\n\n# review-agent-governance — Setup\n\nGate AI agent review actions (PR reviews, comments, merges, CI edits) behind\nexplicit human approval. Every attempt, approved or denied, produces an\nEd25519-signed receipt.\n\n## When to use this plugin\n\nInstall it in projects where a Claude Code agent:\n\n- Reviews, comments on, or merges pull requests (`gh pr review`, `gh pr merge`)\n- Triages issues (`gh issue comment`, `gh issue close`)\n- Publishes releases (`gh release create`)\n- Modifies CI configuration (`.github\u002Fworkflows\u002F`, `.gitlab-ci.yml`)\n- Pushes to protected branches (`main`, `master`, `release`, `production`)\n- Posts to external notification surfaces (Slack webhooks, Discord)\n\nIf the agent is only doing local file edits and running tests, this plugin is\noverkill. Use `protect-mcp` for general tool-call policy enforcement and skip\nthis one.\n\n## One-time setup\n\n### 1. Install the plugin\n\n```bash\nclaude plugin install wshobson\u002Fagents\u002Freview-agent-governance\n```\n\n### 2. Copy the default policy to your project\n\n```bash\ncp .claude\u002Fplugins\u002Freview-agent-governance\u002Fpolicies\u002Freview-agent-governance.cedar \\\n   .\u002Freview-governance.cedar\n```\n\nYou can edit this file to match your project's specific rules. See\n`..\u002Fagents\u002Freview-policy-author.md` for guidance on authoring review\npolicies.\n\n### 3. Create a receipts directory and sign key\n\n```bash\nmkdir -p .\u002Freview-receipts\necho \".\u002Freview-receipts\u002F\" >> .gitignore\necho \".\u002Freview-governance.key\" >> .gitignore\necho \".\u002F.review-approved\" >> .gitignore\n```\n\nThe first invocation of `protect-mcp sign` will create the key. Commit the\npublic key from the first receipt so auditors can verify later.\n\n## Per-session workflow\n\nThe Cedar policy denies review-surface actions unconditionally. To approve\na specific action, open an approval window before it and close it after.\n\n### Flag file (simplest)\n\n```bash\n# Before the action you want to approve\ntouch .\u002F.review-approved\n\n# Let Claude Code run the review \u002F comment \u002F merge\n\n# Immediately after\nrm .\u002F.review-approved\n```\n\n### Slash command (from within Claude Code)\n\n```\n\u002Fapprove-review \"Reviewing PR #123 authored by contributor X\"\n```\n\nThis creates `.\u002F.review-approved` with the given reason embedded as a note,\nand writes a human-approved receipt to the chain. A follow-up `rm` is still\nneeded to close the window.\n\n### Dry-run everything (force full policy evaluation)\n\nIf you want every tool call to go through Cedar with no approval bypass:\n\n```bash\nexport REVIEW_APPROVAL_FLAG=.\u002F.never-approve\n```\n\nAny tool call matching a forbid rule will be denied; approved windows have\nno effect. Useful for CI or for a locked-down audit run.\n\n## Verifying the chain\n\nList all receipts:\n\n```bash\nls -la .\u002Freview-receipts\u002F\n```\n\nVerify the entire chain offline:\n\n```bash\nnpx @veritasacta\u002Fverify .\u002Freview-receipts\u002F*.json\n```\n\nExit 0 means every receipt is authentic and the chain is intact. Exit 1\nmeans one receipt has been tampered with. Exit 2 means a receipt is\nmalformed.\n\nLook at recent denials:\n\n```\n\u002Flist-pending\n```\n\nWithin Claude Code this slash command walks the receipt chain and prints\nany recent `decision: deny` entries with the tool name, command pattern,\nand timestamp.\n\n## Example: approving a PR review\n\n```bash\n# 1. Human reviews the agent's proposed comment\n$ \u002Flist-pending\n  Recent denials:\n  - 2026-04-17T14:23:01Z  Bash \"gh pr review 42 --approve --body 'LGTM'\"\n  - 2026-04-17T14:23:02Z  Bash \"gh pr comment 42 --body 'Looking good'\"\n\n# 2. Human decides the first one is appropriate, approves it\n$ \u002Fapprove-review \"Approving LGTM on PR 42 after visual inspection\"\n  .\u002F.review-approved created\n\n# 3. Agent retries the action; this time it succeeds\n$ agent: gh pr review 42 --approve --body \"LGTM\"\n  [receipt: rec_XXX, decision=allow, reason=human_approved]\n\n# 4. Human closes the window\n$ rm .\u002F.review-approved\n```\n\nEvery step is in the receipt chain. The chain is offline-verifiable for\nregulators, counterparties, or downstream auditors who want to confirm\nthat no review action bypassed the human gate.\n\n## Composing with protect-mcp\n\nIf both plugins are installed, run them side by side:\n\n```json\n{\n  \"hooks\": {\n    \"PreToolUse\": [\n      {\n        \"matcher\": \".*\",\n        \"hooks\": [\n          {\n            \"type\": \"command\",\n            \"command\": \"npx protect-mcp@0.5.5 evaluate --policy .\u002Fprotect.cedar --tool \\\"$TOOL_NAME\\\" --input \\\"$TOOL_INPUT\\\" --fail-on-missing-policy false\"\n          }\n        ]\n      },\n      {\n        \"matcher\": \".*\",\n        \"hooks\": [\n          {\n            \"type\": \"command\",\n            \"command\": \"if [ -f .\u002F.review-approved ]; then exit 0; fi; npx protect-mcp@0.5.5 evaluate --policy .\u002Freview-governance.cedar --tool \\\"$TOOL_NAME\\\" --input \\\"$TOOL_INPUT\\\" --fail-on-missing-policy false\"\n          }\n        ]\n      }\n    ]\n  }\n}\n```\n\nBoth hooks must pass for the tool call to proceed. Cedar deny in either\npolicy blocks it.\n\n## Standards\n\n- **Ed25519** — RFC 8032 (digital signatures)\n- **JCS** — RFC 8785 (deterministic JSON canonicalization)\n- **Cedar** — AWS's open authorization policy language\n- **IETF draft** — [draft-farley-acta-signed-receipts](https:\u002F\u002Fdatatracker.ietf.org\u002Fdoc\u002Fdraft-farley-acta-signed-receipts\u002F)\n","# review-agent-governance — Setup\n\nGate AI agent review actions (PR reviews, comments, merges, CI edits) behind\nexplicit human approval. Every attempt, approved or denied, produces an\nEd25519-signed receipt.\n\n## When to use this plugin\n\nInstall it in projects where a Claude Code agent:\n\n- Reviews, comments on, or merges pull requests (`gh pr review`, `gh pr merge`)\n- Triages issues (`gh issue comment`, `gh issue close`)\n- Publishes releases (`gh release create`)\n- Modifies CI configuration (`.github\u002Fworkflows\u002F`, `.gitlab-ci.yml`)\n- Pushes to protected branches (`main`, `master`, `release`, `production`)\n- Posts to external notification surfaces (Slack webhooks, Discord)\n\nIf the agent is only doing local file edits and running tests, this plugin is\noverkill. Use `protect-mcp` for general tool-call policy enforcement and skip\nthis one.\n\n## One-time setup\n\n### 1. Install the plugin\n\n```bash\nclaude plugin install wshobson\u002Fagents\u002Freview-agent-governance\n```\n\n### 2. Copy the default policy to your project\n\n```bash\ncp .claude\u002Fplugins\u002Freview-agent-governance\u002Fpolicies\u002Freview-agent-governance.cedar \\\n   .\u002Freview-governance.cedar\n```\n\nYou can edit this file to match your project's specific rules. See\n`..\u002Fagents\u002Freview-policy-author.md` for guidance on authoring review\npolicies.\n\n### 3. Create a receipts directory and sign key\n\n```bash\nmkdir -p .\u002Freview-receipts\necho \".\u002Freview-receipts\u002F\" >> .gitignore\necho \".\u002Freview-governance.key\" >> .gitignore\necho \".\u002F.review-approved\" >> .gitignore\n```\n\nThe first invocation of `protect-mcp sign` will create the key. Commit the\npublic key from the first receipt so auditors can verify later.\n\n## Per-session workflow\n\nThe Cedar policy denies review-surface actions unconditionally. To approve\na specific action, open an approval window before it and close it after.\n\n### Flag file (simplest)\n\n```bash\n# Before the action you want to approve\ntouch .\u002F.review-approved\n\n# Let Claude Code run the review \u002F comment \u002F merge\n\n# Immediately after\nrm .\u002F.review-approved\n```\n\n### Slash command (from within Claude Code)\n\n```\n\u002Fapprove-review \"Reviewing PR #123 authored by contributor X\"\n```\n\nThis creates `.\u002F.review-approved` with the given reason embedded as a note,\nand writes a human-approved receipt to the chain. A follow-up `rm` is still\nneeded to close the window.\n\n### Dry-run everything (force full policy evaluation)\n\nIf you want every tool call to go through Cedar with no approval bypass:\n\n```bash\nexport REVIEW_APPROVAL_FLAG=.\u002F.never-approve\n```\n\nAny tool call matching a forbid rule will be denied; approved windows have\nno effect. Useful for CI or for a locked-down audit run.\n\n## Verifying the chain\n\nList all receipts:\n\n```bash\nls -la .\u002Freview-receipts\u002F\n```\n\nVerify the entire chain offline:\n\n```bash\nnpx @veritasacta\u002Fverify .\u002Freview-receipts\u002F*.json\n```\n\nExit 0 means every receipt is authentic and the chain is intact. Exit 1\nmeans one receipt has been tampered with. Exit 2 means a receipt is\nmalformed.\n\nLook at recent denials:\n\n```\n\u002Flist-pending\n```\n\nWithin Claude Code this slash command walks the receipt chain and prints\nany recent `decision: deny` entries with the tool name, command pattern,\nand timestamp.\n\n## Example: approving a PR review\n\n```bash\n# 1. Human reviews the agent's proposed comment\n$ \u002Flist-pending\n  Recent denials:\n  - 2026-04-17T14:23:01Z  Bash \"gh pr review 42 --approve --body 'LGTM'\"\n  - 2026-04-17T14:23:02Z  Bash \"gh pr comment 42 --body 'Looking good'\"\n\n# 2. Human decides the first one is appropriate, approves it\n$ \u002Fapprove-review \"Approving LGTM on PR 42 after visual inspection\"\n  .\u002F.review-approved created\n\n# 3. Agent retries the action; this time it succeeds\n$ agent: gh pr review 42 --approve --body \"LGTM\"\n  [receipt: rec_XXX, decision=allow, reason=human_approved]\n\n# 4. Human closes the window\n$ rm .\u002F.review-approved\n```\n\nEvery step is in the receipt chain. The chain is offline-verifiable for\nregulators, counterparties, or downstream auditors who want to confirm\nthat no review action bypassed the human gate.\n\n## Composing with protect-mcp\n\nIf both plugins are installed, run them side by side:\n\n```json\n{\n  \"hooks\": {\n    \"PreToolUse\": [\n      {\n        \"matcher\": \".*\",\n        \"hooks\": [\n          {\n            \"type\": \"command\",\n            \"command\": \"npx protect-mcp@0.5.5 evaluate --policy .\u002Fprotect.cedar --tool \\\"$TOOL_NAME\\\" --input \\\"$TOOL_INPUT\\\" --fail-on-missing-policy false\"\n          }\n        ]\n      },\n      {\n        \"matcher\": \".*\",\n        \"hooks\": [\n          {\n            \"type\": \"command\",\n            \"command\": \"if [ -f .\u002F.review-approved ]; then exit 0; fi; npx protect-mcp@0.5.5 evaluate --policy .\u002Freview-governance.cedar --tool \\\"$TOOL_NAME\\\" --input \\\"$TOOL_INPUT\\\" --fail-on-missing-policy false\"\n          }\n        ]\n      }\n    ]\n  }\n}\n```\n\nBoth hooks must pass for the tool call to proceed. Cedar deny in either\npolicy blocks it.\n\n## Standards\n\n- **Ed25519** — RFC 8032 (digital signatures)\n- **JCS** — RFC 8785 (deterministic JSON canonicalization)\n- **Cedar** — AWS's open authorization policy language\n- **IETF draft** — [draft-farley-acta-signed-receipts](https:\u002F\u002Fdatatracker.ietf.org\u002Fdoc\u002Fdraft-farley-acta-signed-receipts\u002F)\n",{"name":5,"description":7},"main","62c7af5ced2c21355d148c243edb6d5921cca1a6",".agents\u002Fskills\u002Freview-agent-setup",8,"https:\u002F\u002Fgithub.com\u002FRudyCity\u002Fsuperagent","https:\u002F\u002Fgithub.com\u002FRudyCity","2026-11-14 22:58:49",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add RudyCity\u002Fsuperagent --skill review-agent-setup",{"tool":36,"command":37},"bunx","bunx skills add RudyCity\u002Fsuperagent --skill review-agent-setup",{"tool":39,"command":40},"pnpm","pnpm dlx skills add RudyCity\u002Fsuperagent --skill review-agent-setup","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FRudyCity\u002Fsuperagent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Freview-agent-setup\u002FSKILL.md",true,[],[45,52,59,66,73,80],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":18},"01M75GP28CM6QCSXSHKFF3NNKS","telegram_bot","Use Telegram Bot when the user asks for Telegram Bot or this provider's API.","https:\u002F\u002Fgithub.com\u002FRudyCity\u002Fsuperagent\u002Fblob\u002Fmain\u002Fmuse-bridge-kit\u002Fskills\u002Ftelegram-bot\u002FSKILL.md",[],[],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":18},"01M75GNZGZYM7NWDV6MBP3HS14","superagent-bridge","Operate the Muse\u003C->superagent Telegram bridge: poll the private group for task_request\u002Ftask_result envelopes, validate senders, and reply with task_batch\u002Ftask_done as Muse (the remote brain).","https:\u002F\u002Fgithub.com\u002FRudyCity\u002Fsuperagent\u002Fblob\u002Fmain\u002Fmuse-bridge-kit\u002Fskills\u002Fsuperagent-bridge\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":18},"01M75GNHN19HJWZ7NAPM5E5JCV","Writing Skills","TDD for process documentation - test with subagents before writing, iterate until bulletproof","https:\u002F\u002Fgithub.com\u002FRudyCity\u002Fsuperagent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwriting-skills\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":18},"01M75GNCQEKVRA4FH161NZPZNB","writing-shape","Take a markdown file of raw material and shape it into an article through a conversational session — drafting candidate openings, growing the piece paragraph by paragraph, arguing about format (lists, tables, callouts, quotes) at each step. Use when the user has a pile of notes, fragments, or a rough draft and wants help turning it into something publishable.","https:\u002F\u002Fgithub.com\u002FRudyCity\u002Fsuperagent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwriting-shape\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":18},"01M75GNAF9NAYCSTBDZDGMK0DZ","Writing Plans","Create detailed implementation plans with bite-sized tasks for engineers with zero codebase context","https:\u002F\u002Fgithub.com\u002FRudyCity\u002Fsuperagent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwriting-plans\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":18},"01M75GN72EV0V5NQAW9CSPFRFH","writing-guidelines","Review docs\u002Fprose for Writing Guidelines compliance. Use when asked to \"review my docs\", \"check writing style\", \"audit prose\", \"review docs voice and tone\", or \"check this page against the writing handbook\".","https:\u002F\u002Fgithub.com\u002FRudyCity\u002Fsuperagent\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwriting-guidelines\u002FSKILL.md",[],[]]