菜单
USE FOR: `$create-review-comment`, ai-create-review-comment, or terse PR-review-comment requests. Infers the PR and routes postman substantive review through guardian/critic without exposing mechanics. DO NOT USE FOR: unrelated tasks, broad rewrites, generated outputs, or posting comments without explicit approval.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
USE FOR: This dotfiles environment and its agent harness: machine setup (Ubuntu, WSL2, macOS, home-manager, nix-darwin), daily Nix operations and upgrade/recovery, missing CLI tools / command not found, operating concepts, clipboard (Vim, Neovim, tmux), Claude Code and Codex CLI config, hooks, MCP, skill installation, postman routing, orchestrator runbooks, tmux workspaces, issue/PR worktrees, pane operations, prompt/review contracts, resume handoff; Agent Skills authoring: add/edit/validate skills, Waza, publishing. DO NOT USE FOR: Nix package authoring (programming).
USE FOR: Guardian/critic native multi-perspective review workflow, peer critic evidence, material-finding convergence, and blocking-finding synthesis. DO NOT USE FOR: implementation, dispatcher fan-out, overrides, or public posting.
USE FOR: Clarify concepts before names harden by fixing concrete referents, roles, sequence, candidate terms, and first-use definitions. Use for terminology-heavy design docs, research synthesis, cause-isolation or mitigation plans, naming decisions, and reasoning-order summaries only when concept/referent ambiguity could distort the work. DO NOT USE FOR: ordinary terminology/glossary editing when referents are stable, simple editing, translation-only work, proofreading, generic summarization/research, implementation, or broad content generation.
USE FOR: Implementation plans and durable task tracking: reduce ambiguity, compare options, parallel investigation, multi-source synthesis, review gates, task artifacts, evidence logs, handoff/resume, and DONE/BLOCKED verification. DO NOT USE FOR: unrelated tasks, broad rewrites outside the request, or generated runtime outputs.
USE FOR: Verifying technical claims, comparing options, and investigating unfamiliar libraries/APIs/tools with cited, confidence-rated evidence. DO NOT USE FOR: implementation, opinion without evidence, or tasks better served by a narrower repo-specific skill (e.g. `data-platform`, `collaboration`).
USE FOR: Prose QA, Vale/Harper, terminology, English/Japanese edits, English-to-Japanese, stable glossaries, rhythm, AI-slop cleanup, publication QA. DO NOT USE FOR: AI detector/humanizer workflows, fresh generation, meaning-changing rewrites, replacing author judgment, publishing, model/cost/privacy, external sharing, or chunking.
| name | create-review-comment |
| license | MIT |
| metadata | {"version":"1.0.0"} |
| description | USE FOR: `$create-review-comment`, ai-create-review-comment, or terse PR-review-comment requests. Infers the PR and routes postman substantive review through guardian/critic without exposing mechanics. DO NOT USE FOR: unrelated tasks, broad rewrites, generated outputs, or posting comments without explicit approval. |
User-facing trigger for drafting Japanese GitHub PR review comments.
$create-review-comment, $create-review-comment #123, and
ai-create-review-comment for this branch all start target inference and
drafting.
Owns target inference, Japanese draft output, and the
no-post-without-approval gate. Review procedure belongs to
subagent-review; GitHub mechanics and path hygiene belong to collaboration.
In tmux-a2a-postman, orchestrator/worker only infer targets and collect PR
context before routing substantive review to guardian.
subagent-review through postman: send the
review package to guardian, let guardian request critic, and never launch
reviewer subagents from orchestrator/worker. Do not ask the user for review
mechanics.