[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6XDE28TPB0Z3YAF7V2NNZZ7":3,"skill-same:01M6XDE28TPB0Z3YAF7V2NNZZ7":65},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":14,"repositoryHtmlUrl":47,"repositoryHomepageUrl":6,"ownerHtmlUrl":48,"ownerBlogUrl":6,"ownerDescription":49,"updatedAt":50,"install":51,"resources":64},"01M6XDE28TPB0Z3YAF7V2NNZZ7","review-prs",null,"Batch-review multiple PRs in parallel: dispatch one sub-agent per PR in an isolated worktree, aggregate results into a summary table. Triggers on: \"review all PRs\", \"check my PRs\", \"PR status\".","kaiohenricunha\u002Fdotbabel","kaiohenricunha","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F69804490?v=4","01M6XCZD37W0KPCDGEA40Y610V","Kaio Cunha","01M6XCZD7SX714D114H3ZPNW09",0,"MIT","https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fplugins\u002Fdotbabel\u002Ftemplates\u002Fclaude\u002Fskills\u002Freview-prs\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36],"review prs","prs","review","dispatch","space","sub-agent","n3","my","triggers","summary","results","check","parallel","table","worktree","batch","pr","status","2026-11-10 10:12:30",false,"---\n# dotbabel:generated projection=sha256:65e3ab0662eadde3b6d725a8259f6f96e940f26ac03d231d0d1e17f47d8aaf35 source=skills\u002Freview-prs\u002FSKILL.md — do not edit directly\nargument-hint: \u003CN1> [N2 N3 ...] — space-separated PR numbers\ndescription: |\n  Batch-review multiple PRs in parallel: dispatch one sub-agent per PR in an isolated worktree, aggregate results into a summary table. Triggers on: \"review all PRs\", \"check my PRs\", \"PR status\".\nname: review-prs\n---\n\nBatch-review a list of PRs in parallel. Each PR gets its own sub-agent running the full `review-pr` workflow (fetch comments → validate → apply fixes → push → resolve threads → CI gate). Results are aggregated into a single summary table.\n\nTrigger: when the user provides a list of PR numbers to review simultaneously, asks to batch-review PRs, or says \"review all of these\".\n\nArguments: `$ARGUMENTS` — space-separated PR numbers (required). Example: `\u002Freview-prs 42 43 44`.\n\n## Steps\n\n### 1. Parse arguments\n\nBind `NUMBERS` from `$ARGUMENTS`. If empty, print usage and stop:\n\n```\nUsage: \u002Freview-prs \u003CN1> [N2 N3 ...]\n```\n\nEcho the target list before doing any network calls: \"Reviewing N PRs: #A #B #C\".\n\n### 2. Pre-flight checks\n\nRun all three checks **before creating any worktree**.\n\n**2a — PR existence and state.** For each PR number:\n\n```bash\ngh pr view \"$N\" --json number,title,headRefName,baseRefName,mergeable,mergeStateStatus,state\n```\n\n- Non-zero exit (PR not found, no access) → mark `preflight-failed: not-found`; add a synthetic result row for that PR and exclude it from worktree\u002Fsub-agent execution.\n- `state != \"OPEN\"` → mark `preflight-failed: not-open`; add a synthetic result row for that PR and exclude it from worktree\u002Fsub-agent execution.\n\nReport any exclusions. Never silently skip a PR: every requested PR must appear in the final aggregate table, including `preflight-failed` rows created here. If zero PRs survive for execution, stop after emitting the aggregate table.\n\n**2b — Merge state classification** (advisory; from the same JSON above):\n\n| `mergeable`   | `mergeStateStatus`    | Tag                             |\n| ------------- | --------------------- | ------------------------------- |\n| `CONFLICTING` | `DIRTY`               | `preflight-warn: conflicts`     |\n| `MERGEABLE`   | `BEHIND`              | `preflight-warn: behind`        |\n| `UNKNOWN`     | any                   | `preflight-warn: unknown-state` |\n| `MERGEABLE`   | `CLEAN` or `UNSTABLE` | (no tag — proceed normally)     |\n\nRecord the tag and pass `mergeStateStatus` into the sub-agent brief; the sub-agent handles rebase (step 9 of review-pr) and CI (step 10) autonomously.\n\n**2c — Worktree collision check.** Run once:\n\n```bash\ngit worktree list\n```\n\nFor each PR N, check if `.claude\u002Fworktrees\u002Fpr-N` appears. If yes: `preflight-warn: worktree-exists` and set `WORKTREE_EXISTS=true` for that PR. The sub-agent reuses the existing worktree safely (the `if [ ! -d ]` guard in review-pr step 5 handles this). If no: `WORKTREE_EXISTS=false`.\n\n**Print the pre-flight summary table before dispatch:**\n\n| PR  | Title | Merge State | Worktree | Pre-flight                       |\n| --- | ----- | ----------- | -------- | -------------------------------- |\n| #42 | ...   | CLEAN       | new      | ok                               |\n| #43 | ...   | DIRTY       | exists   | warn: conflicts, worktree-exists |\n\nOnly surviving (non-`preflight-failed`) PRs proceed.\n\n### 3. Batch into rounds of 6\n\nSplit surviving PRs into rounds of at most 6. Print the plan before dispatching:\n\n```\nRound 1: #42, #43, #44, #45, #46, #47\nRound 2: #48\n```\n\n### 4. Dispatch parallel sub-agents\n\nFor each round: emit a **single coordinator message with one `Agent` tool call per PR** — all calls in that round in one message. Use `subagent_type: \"general-purpose\"`. Wait for all agents in the round to complete before starting the next.\n\nConstruct the following brief for each PR, substituting real values for `N`, `TITLE`, `BASE_REF`, `MERGE_STATE_STATUS`, and `WORKTREE_EXISTS`:\n\n---\n\n```\nYou are reviewing PR #N (\"TITLE\") in repo $(gh repo view --json nameWithOwner -q .nameWithOwner).\n\nWorking directory: $(git rev-parse --show-toplevel)\nWorktree path: .claude\u002Fworktrees\u002Fpr-N\nWorktree already exists: WORKTREE_EXISTS\nBase ref: BASE_REF\nMerge state at dispatch: MERGE_STATE_STATUS\n\nFollow the review-pr command workflow exactly — all 15 steps — with these constraints:\n\nAUTONOMY\n- Do NOT merge. The user merges explicitly via `\u002Fmerge-pr N` after reviewing the aggregate table.\n- Do NOT prompt the user. Make autonomous decisions throughout.\n- If a decision requires user judgement (e.g. an ambiguous design change), note it in `blocker`\n  and continue with the rest of the review. Do not halt.\n\nWORKTREE\n- If WORKTREE_EXISTS is true, skip `git worktree add` and use the existing path as-is.\n- If MERGE_STATE_STATUS is BEHIND or DIRTY, rebase onto the base ref before collecting comments\n  (review-pr step 9 covers this — do it first, before step 2, when the branch is conflicting).\n\nOUTPUT\nAfter completing step 15, emit exactly ONE JSON object to stdout (no other text after it):\n\n{\n  \"pr\": N,\n  \"title\": \"TITLE\",\n  \"comments\": \u003Ctotal comments fetched>,\n  \"valid\": \u003Ccount valid issues>,\n  \"false_pos\": \u003Ccount false positives>,\n  \"fixed\": \u003Ccount fixes applied>,\n  \"security\": \"clean|findings\",\n  \"ci\": \"green|fixed|blocked|flaky|skipped\",\n  \"test_plan\": \"verified|missing|partial|skipped\",\n  \"conflicts\": \"none|resolved|unresolved\",\n  \"status\": \"reviewed|blocked|push-failed|test-plan-missing|conflicts-unresolved|sub-agent-failed|preflight-failed\",\n  \"evidence_url\": \"\u003CCI run URL or test output reference>\",\n  \"blocker\": null\n}\n\nFAILURE MODES\n- Push failure (step 7): set status \"push-failed\", stop — do not post replies or resolve threads.\n- Test plan missing: set status \"test-plan-missing\"; include evidence_url if available.\n- Merge conflicts left unresolved: set status \"conflicts-unresolved\"; set blocker to a one-line explanation.\n- Preflight\u002Fsetup failure before the review can run: set status \"preflight-failed\", set blocker to a\n  one-line explanation, still emit the JSON. Use zero counts for fields that were never collected.\n- Sub-agent execution failure after start but before a normal result is produced: set status\n  \"sub-agent-failed\", set blocker to a one-line explanation, still emit the JSON. Populate\n  completed counts best-effort from work finished before the failure.\n- Sandbox blocks file writes: emit JSON to stdout regardless.\n- Any other unrecoverable error: set status \"blocked\", set blocker to a one-line explanation,\n  still emit the JSON.\n```\n\n---\n\n### 5. Collect results and handle partial failures\n\nAfter each round, parse each sub-agent's stdout for the result JSON.\n\n| Outcome               | Action                                                                              |\n| --------------------- | ----------------------------------------------------------------------------------- |\n| Valid JSON            | Store for aggregate table                                                           |\n| No output \u002F crash     | `status: sub-agent-failed`, `blocker: \"no output from sub-agent\"`                   |\n| Malformed JSON        | `status: sub-agent-failed`, `blocker: \"parse error: \u003Cfirst 100 chars of output>\"`   |\n| `status: push-failed` | Record as-is; add note: \"commits staged locally — run `\u002Freview-pr N` to retry push\" |\n\nNever silently skip a PR. Every PR gets a row in the aggregate table.\n\n### 6. Aggregate summary table\n\nRender one row per PR using the collected JSON:\n\n| PR  | Title | Comments | Valid | False Pos | Fixed | Security | CI  | Test Plan | Conflicts | Status |\n| --- | ----- | -------- | ----- | --------- | ----- | -------- | --- | --------- | --------- | ------ |\n\nStatus values: `reviewed`, `blocked`, `push-failed`, `test-plan-missing`, `conflicts-unresolved`, `preflight-failed`, `sub-agent-failed`.\n\nA PR may only be marked `reviewed` if: push succeeded, test plan verified, every active criterion passed in review-pr step 14, no unresolved CI failures, branch not conflicting (same gate as review-pr step 15).\n\nIf any PRs have `sub-agent-failed`: end the table with — \"For failed PRs, run `\u002Freview-pr N` individually.\"\n\n### 7. Cleanup\n\nPrint (do not auto-run) the cleanup command for every worktree created during this run:\n\n```bash\ngit worktree remove .claude\u002Fworktrees\u002Fpr-N   # for each N\n```\n\n## Rules\n\n- **Never merge** from inside a sub-agent or from the coordinator. Use `\u002Fmerge-pr N` or `\u002Freview-pr N` explicitly for each PR after reviewing the table.\n- **Parallelism cap:** 6 concurrent sub-agents per round. Batch the rest into subsequent rounds.\n- **Never force-push** from sub-agents. If rebase produces a conflict the sub-agent cannot resolve, it marks `conflicts: unresolved` and stops.\n- **Worktree recreation:** if a worktree path disappears mid-run, the sub-agent's `if [ ! -d ]` guard recreates it.\n- **Sandbox write blocks:** sub-agents emit JSON to stdout; the coordinator captures from stdout, not from files.\n- **Every Status row** must cite the `evidence_url` from the sub-agent's JSON (CI run URL or test output).\n- **Pre-flight failures are non-fatal** to the batch — removed PRs are reported in the pre-flight table and excluded from dispatch. The remaining PRs proceed.\n\n## Compute scope\n\nThe coordinator's consumer requirement is inheritance. It sets no model or effort,\nand native skill frontmatter does not enforce compute. Keep the existing generic\nper-PR workers, their inheritance, rounds and review workflow. Record any observed\ncoordinator configuration separately from each worker's observation. Do not infer\na worker's configuration from the coordinator or from an inert skill selector;\nmissing observations remain unknown. Keep the existing worker result contract.\n","Batch-review a list of PRs in parallel. Each PR gets its own sub-agent running the full `review-pr` workflow (fetch comments → validate → apply fixes → push → resolve threads → CI gate). Results are aggregated into a single summary table.\n\nTrigger: when the user provides a list of PR numbers to review simultaneously, asks to batch-review PRs, or says \"review all of these\".\n\nArguments: `$ARGUMENTS` — space-separated PR numbers (required). Example: `\u002Freview-prs 42 43 44`.\n\n## Steps\n\n### 1. Parse arguments\n\nBind `NUMBERS` from `$ARGUMENTS`. If empty, print usage and stop:\n\n```\nUsage: \u002Freview-prs \u003CN1> [N2 N3 ...]\n```\n\nEcho the target list before doing any network calls: \"Reviewing N PRs: #A #B #C\".\n\n### 2. Pre-flight checks\n\nRun all three checks **before creating any worktree**.\n\n**2a — PR existence and state.** For each PR number:\n\n```bash\ngh pr view \"$N\" --json number,title,headRefName,baseRefName,mergeable,mergeStateStatus,state\n```\n\n- Non-zero exit (PR not found, no access) → mark `preflight-failed: not-found`; add a synthetic result row for that PR and exclude it from worktree\u002Fsub-agent execution.\n- `state != \"OPEN\"` → mark `preflight-failed: not-open`; add a synthetic result row for that PR and exclude it from worktree\u002Fsub-agent execution.\n\nReport any exclusions. Never silently skip a PR: every requested PR must appear in the final aggregate table, including `preflight-failed` rows created here. If zero PRs survive for execution, stop after emitting the aggregate table.\n\n**2b — Merge state classification** (advisory; from the same JSON above):\n\n| `mergeable`   | `mergeStateStatus`    | Tag                             |\n| ------------- | --------------------- | ------------------------------- |\n| `CONFLICTING` | `DIRTY`               | `preflight-warn: conflicts`     |\n| `MERGEABLE`   | `BEHIND`              | `preflight-warn: behind`        |\n| `UNKNOWN`     | any                   | `preflight-warn: unknown-state` |\n| `MERGEABLE`   | `CLEAN` or `UNSTABLE` | (no tag — proceed normally)     |\n\nRecord the tag and pass `mergeStateStatus` into the sub-agent brief; the sub-agent handles rebase (step 9 of review-pr) and CI (step 10) autonomously.\n\n**2c — Worktree collision check.** Run once:\n\n```bash\ngit worktree list\n```\n\nFor each PR N, check if `.claude\u002Fworktrees\u002Fpr-N` appears. If yes: `preflight-warn: worktree-exists` and set `WORKTREE_EXISTS=true` for that PR. The sub-agent reuses the existing worktree safely (the `if [ ! -d ]` guard in review-pr step 5 handles this). If no: `WORKTREE_EXISTS=false`.\n\n**Print the pre-flight summary table before dispatch:**\n\n| PR  | Title | Merge State | Worktree | Pre-flight                       |\n| --- | ----- | ----------- | -------- | -------------------------------- |\n| #42 | ...   | CLEAN       | new      | ok                               |\n| #43 | ...   | DIRTY       | exists   | warn: conflicts, worktree-exists |\n\nOnly surviving (non-`preflight-failed`) PRs proceed.\n\n### 3. Batch into rounds of 6\n\nSplit surviving PRs into rounds of at most 6. Print the plan before dispatching:\n\n```\nRound 1: #42, #43, #44, #45, #46, #47\nRound 2: #48\n```\n\n### 4. Dispatch parallel sub-agents\n\nFor each round: emit a **single coordinator message with one `Agent` tool call per PR** — all calls in that round in one message. Use `subagent_type: \"general-purpose\"`. Wait for all agents in the round to complete before starting the next.\n\nConstruct the following brief for each PR, substituting real values for `N`, `TITLE`, `BASE_REF`, `MERGE_STATE_STATUS`, and `WORKTREE_EXISTS`:\n\n---\n\n```\nYou are reviewing PR #N (\"TITLE\") in repo $(gh repo view --json nameWithOwner -q .nameWithOwner).\n\nWorking directory: $(git rev-parse --show-toplevel)\nWorktree path: .claude\u002Fworktrees\u002Fpr-N\nWorktree already exists: WORKTREE_EXISTS\nBase ref: BASE_REF\nMerge state at dispatch: MERGE_STATE_STATUS\n\nFollow the review-pr command workflow exactly — all 15 steps — with these constraints:\n\nAUTONOMY\n- Do NOT merge. The user merges explicitly via `\u002Fmerge-pr N` after reviewing the aggregate table.\n- Do NOT prompt the user. Make autonomous decisions throughout.\n- If a decision requires user judgement (e.g. an ambiguous design change), note it in `blocker`\n  and continue with the rest of the review. Do not halt.\n\nWORKTREE\n- If WORKTREE_EXISTS is true, skip `git worktree add` and use the existing path as-is.\n- If MERGE_STATE_STATUS is BEHIND or DIRTY, rebase onto the base ref before collecting comments\n  (review-pr step 9 covers this — do it first, before step 2, when the branch is conflicting).\n\nOUTPUT\nAfter completing step 15, emit exactly ONE JSON object to stdout (no other text after it):\n\n{\n  \"pr\": N,\n  \"title\": \"TITLE\",\n  \"comments\": \u003Ctotal comments fetched>,\n  \"valid\": \u003Ccount valid issues>,\n  \"false_pos\": \u003Ccount false positives>,\n  \"fixed\": \u003Ccount fixes applied>,\n  \"security\": \"clean|findings\",\n  \"ci\": \"green|fixed|blocked|flaky|skipped\",\n  \"test_plan\": \"verified|missing|partial|skipped\",\n  \"conflicts\": \"none|resolved|unresolved\",\n  \"status\": \"reviewed|blocked|push-failed|test-plan-missing|conflicts-unresolved|sub-agent-failed|preflight-failed\",\n  \"evidence_url\": \"\u003CCI run URL or test output reference>\",\n  \"blocker\": null\n}\n\nFAILURE MODES\n- Push failure (step 7): set status \"push-failed\", stop — do not post replies or resolve threads.\n- Test plan missing: set status \"test-plan-missing\"; include evidence_url if available.\n- Merge conflicts left unresolved: set status \"conflicts-unresolved\"; set blocker to a one-line explanation.\n- Preflight\u002Fsetup failure before the review can run: set status \"preflight-failed\", set blocker to a\n  one-line explanation, still emit the JSON. Use zero counts for fields that were never collected.\n- Sub-agent execution failure after start but before a normal result is produced: set status\n  \"sub-agent-failed\", set blocker to a one-line explanation, still emit the JSON. Populate\n  completed counts best-effort from work finished before the failure.\n- Sandbox blocks file writes: emit JSON to stdout regardless.\n- Any other unrecoverable error: set status \"blocked\", set blocker to a one-line explanation,\n  still emit the JSON.\n```\n\n---\n\n### 5. Collect results and handle partial failures\n\nAfter each round, parse each sub-agent's stdout for the result JSON.\n\n| Outcome               | Action                                                                              |\n| --------------------- | ----------------------------------------------------------------------------------- |\n| Valid JSON            | Store for aggregate table                                                           |\n| No output \u002F crash     | `status: sub-agent-failed`, `blocker: \"no output from sub-agent\"`                   |\n| Malformed JSON        | `status: sub-agent-failed`, `blocker: \"parse error: \u003Cfirst 100 chars of output>\"`   |\n| `status: push-failed` | Record as-is; add note: \"commits staged locally — run `\u002Freview-pr N` to retry push\" |\n\nNever silently skip a PR. Every PR gets a row in the aggregate table.\n\n### 6. Aggregate summary table\n\nRender one row per PR using the collected JSON:\n\n| PR  | Title | Comments | Valid | False Pos | Fixed | Security | CI  | Test Plan | Conflicts | Status |\n| --- | ----- | -------- | ----- | --------- | ----- | -------- | --- | --------- | --------- | ------ |\n\nStatus values: `reviewed`, `blocked`, `push-failed`, `test-plan-missing`, `conflicts-unresolved`, `preflight-failed`, `sub-agent-failed`.\n\nA PR may only be marked `reviewed` if: push succeeded, test plan verified, every active criterion passed in review-pr step 14, no unresolved CI failures, branch not conflicting (same gate as review-pr step 15).\n\nIf any PRs have `sub-agent-failed`: end the table with — \"For failed PRs, run `\u002Freview-pr N` individually.\"\n\n### 7. Cleanup\n\nPrint (do not auto-run) the cleanup command for every worktree created during this run:\n\n```bash\ngit worktree remove .claude\u002Fworktrees\u002Fpr-N   # for each N\n```\n\n## Rules\n\n- **Never merge** from inside a sub-agent or from the coordinator. Use `\u002Fmerge-pr N` or `\u002Freview-pr N` explicitly for each PR after reviewing the table.\n- **Parallelism cap:** 6 concurrent sub-agents per round. Batch the rest into subsequent rounds.\n- **Never force-push** from sub-agents. If rebase produces a conflict the sub-agent cannot resolve, it marks `conflicts: unresolved` and stops.\n- **Worktree recreation:** if a worktree path disappears mid-run, the sub-agent's `if [ ! -d ]` guard recreates it.\n- **Sandbox write blocks:** sub-agents emit JSON to stdout; the coordinator captures from stdout, not from files.\n- **Every Status row** must cite the `evidence_url` from the sub-agent's JSON (CI run URL or test output).\n- **Pre-flight failures are non-fatal** to the batch — removed PRs are reported in the pre-flight table and excluded from dispatch. The remaining PRs proceed.\n\n## Compute scope\n\nThe coordinator's consumer requirement is inheritance. It sets no model or effort,\nand native skill frontmatter does not enforce compute. Keep the existing generic\nper-PR workers, their inheritance, rounds and review workflow. Record any observed\ncoordinator configuration separately from each worker's observation. Do not infer\na worker's configuration from the coordinator or from an inert skill selector;\nmissing observations remain unknown. Keep the existing worker result contract.\n",{"name":5,"description":42,"argument-hint":43},"Batch-review multiple PRs in parallel: dispatch one sub-agent per PR in an isolated worktree, aggregate results into a summary table. Triggers on: \"review all PRs\", \"check my PRs\", \"PR status\".\n","\u003CN1> [N2 N3 ...] — space-separated PR numbers","main","91c337164997b99943fbcc64e8e362577b67bc81","plugins\u002Fdotbabel\u002Ftemplates\u002Fclaude\u002Fskills\u002Freview-prs","https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel","https:\u002F\u002Fgithub.com\u002Fkaiohenricunha","I'm a Platform\u002FInfra engineer who happens to work in cybersec and write Go code.","2026-10-26 14:12:51",{"source":8,"skillName":5,"commands":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add kaiohenricunha\u002Fdotbabel --skill review-prs",{"tool":57,"command":58},"bunx","bunx skills add kaiohenricunha\u002Fdotbabel --skill review-prs",{"tool":60,"command":61},"pnpm","pnpm dlx skills add kaiohenricunha\u002Fdotbabel --skill review-prs","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fplugins\u002Fdotbabel\u002Ftemplates\u002Fclaude\u002Fskills\u002Freview-prs\u002FSKILL.md",true,[],[66,97,130,152,174,197],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":77,"publishedAt":37},"01M6XDQ7QMASPFZ355MYKCD06T","yolo","Start temporary autonomy for the current task or an explicit scope with a required --for expiry. Codex permits scoped pushes, merges, deploys, and releases after strict testing and validation; Full access is a separate runtime setting. Claude Code uses a session permission hook with a protected-action denylist.","https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fskills\u002Fyolo\u002FSKILL.md",[72],{"categoryNo":73,"categoryName":74,"taxonomyType":75,"taxonomyTypeDesc":76},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[68,78,79,80,81,82,83,84,85,86,87,88,89,90,91,92,93,94,95,96],"testing","merge","code","start","access","session","ops","autonomy","releases","permission","full","runtime","scope","devex","hook","true","action","for","scoped",{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":111,"publishedAt":37},"01M6XDQ1N21VE4KH98JWGZ7GN9","veracity-audit","Audit a data pipeline for Veracity and Value. Dispatches data-scientist, compliance-auditor, and data-engineer agents with project context injected at dispatch time. All source paths are supplied via flags — no defaults, no project assumptions. Subcommands: audit (full pipeline walk), score-check (scoring math only), gate-check (gate coverage only), source-trace \u003Clabel> (single source end-to-end). Invoke when: \"audit pipeline\", \"veracity check\", \"scoring math correct?\", \"check gates\", \"trace source\", \"verify quality gates\", \"formula correct?\".","https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fskills\u002Fveracity-audit\u002FSKILL.md",[103,108],{"categoryNo":104,"categoryName":105,"taxonomyType":106,"taxonomyTypeDesc":107},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":109,"categoryName":110,"taxonomyType":75,"taxonomyTypeDesc":76},"01JBSEEDCAT000000000000037","律师与法务",[112,113,78,21,114,115,116,117,118,119,120,121,122,123,124,125,126,127,128,129],"audit","veracity audit","data pipeline","pipeline","Bash","math","coverage","only","engineer","formula","scoring","time","project","worker","end","at","invoke","when",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":37},"01M6XDPVDKBR376C06CEK9BC5S","validate-spec","Audit an already-implemented spec against the codebase. Walks each constraint (ARCH-N, PERF-N, KD-N, etc.) and acceptance criterion, grounds findings in file:line evidence, runs the spec.json acceptance_commands, and writes a single audit doc to docs\u002Faudits\u002F. Use whenever the user asks to \"validate a spec\", \"audit a spec\", \"check if spec is implemented\", \"verify the spec is done\", \"is this spec really done\", or otherwise wants closure on spec-driven work. Read-only against the spec — produces an audit, never modifies the spec itself.","https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fskills\u002Fvalidate-spec\u002FSKILL.md",[],[137,138,139,78,21,140,141,112,116,142,143,144,119,145,146,147,148,149,150,151],"spec","validate","validate spec","run","acceptance","work","read","never","max","done","arch","line","2025","spec-driven","closure",{"skillNo":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":156,"categories":157,"keywords":161,"publishedAt":37},"01M6XDPMMECH82RAW553Y94HDS","terragrunt-specialist","Deep-dive Terragrunt hierarchy review, DRY pattern audits, and run-all orchestration analysis. Use for structured investigations of multi-environment Terragrunt layouts, dependency graphs, remote state config, and hook correctness. Triggers on: \"Terragrunt audit\", \"run-all review\", \"dependency block\", \"DRY pattern review\", \"env hierarchy audit\", \"mock_outputs\", \"terragrunt hooks\".","https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fskills\u002Fterragrunt-specialist\u002FSKILL.md",[158],{"categoryNo":159,"categoryName":160,"taxonomyType":106,"taxonomyTypeDesc":107},"01JBSEEDCAT000000000000011","运维与部署",[162,163,164,21,165,166,140,112,167,116,143,168,169,145,170,171,149,172,127,173],"terragrunt","specialist","terragrunt specialist","orchestration","debugging","analysis","dependency","hooks","deep","dry","remote","hierarchy",{"skillNo":175,"name":176,"nameZh":6,"description":177,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":178,"categories":179,"keywords":187,"publishedAt":37},"01M6XDPFJS2HGSE13RXF1HV8S7","terraform-specialist","Deep-dive Terraform architecture review, module design, state management, and migration. Use for structured investigations of Terraform workspaces, provider configuration, module coupling, import workflows, and test coverage. Triggers on: \"Terraform audit\", \"module review\", \"state management\", \"Terraform import\", \"workspace design\", \"provider config review\", \"Terraform testing\".","https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fskills\u002Fterraform-specialist\u002FSKILL.md",[180,183,184],{"categoryNo":181,"categoryName":182,"taxonomyType":106,"taxonomyTypeDesc":107},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":159,"categoryName":160,"taxonomyType":106,"taxonomyTypeDesc":107},{"categoryNo":185,"categoryName":186,"taxonomyType":106,"taxonomyTypeDesc":107},"01JBSEEDCAT000000000000015","视觉设计",[188,189,163,78,190,21,191,192,193,166,112,116,143,118,194,195,170,196,149,127],"terraform","terraform specialist","design","workflows","architecture","architecture review","test coverage","workspaces","problem",{"skillNo":198,"name":137,"nameZh":6,"description":199,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":200,"categories":201,"keywords":206,"publishedAt":37},"01M6XDP7V6H8WYPSXVEKYE6HJ6","Create structured engineering specs through interactive pairing. Use when the user wants to create a spec, design doc, technical specification, architecture document, RFC, or engineering plan. Triggers on \"let's spec this out\", \"create a spec\", \"design doc\", \"write a technical plan\", \"plan the architecture\". Works for greenfield and brownfield projects. Outputs to docs\u002Fspecs\u002F.","https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fskills\u002Fspec\u002FSKILL.md",[202,203],{"categoryNo":185,"categoryName":186,"taxonomyType":106,"taxonomyTypeDesc":107},{"categoryNo":204,"categoryName":205,"taxonomyType":75,"taxonomyTypeDesc":76},"01JBSEEDCAT000000000000032","设计师",[137,190,207,192,208,209,210,211,212,213,214,215,27,216,217,95,218,219,220,221],"component","create","plan","projects","write","interactive","use","document","specification","opus","technical specification","trade-offs","technical plan","outputs","frontier"]