菜单
Delegate a code review to your own scope's critic agent. Ensures ai-workers panes are running for YOUR scope, then sends the request to <scope>@critic. Use for code review, diff review, quality checks. Never borrows agents from other scopes.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Delegate deep domain analysis, architecture planning, or complex decisions to your own scope's expert agent (claude-opus). Ensures the expert is running for YOUR scope. Use for architectural decisions, multi-step planning, tradeoff evaluation, domain modeling. Never borrows agents from other scopes.
Full feature development cycle with herdr-managed agent panes. Ensures an ai-workers tab exists with coder, researcher, and critic panes, then orchestrates implement-review loop via pi-link. Use when you want a persistent multi-agent workspace managed by herdr.
Delegate a research task to your own scope's researcher agent. Ensures ai-workers panes are running for YOUR scope, then sends the request to <scope>@researcher. Use for codebase exploration, external references, pattern lookup. Never borrows agents from other scopes.
Analyze colleague feedback for relevance, objectivity, and practical value. Use when evaluating code review comments, architectural feedback, or any critique from a peer before deciding what to act on.
Full feature development cycle with multi-agent collaboration — researcher, coder, and reviewer. Use when implementing a non-trivial feature that benefits from research, iterative coding, and independent review.
Delegate a task to the most suitable connected agent via link_prompt and return the result to the user. Use when you want to route a request to a specialist colleague on the pi-link network.
| name | team-review |
| description | Delegate a code review to your own scope's critic agent. Ensures ai-workers panes are running for YOUR scope, then sends the request to <scope>@critic. Use for code review, diff review, quality checks. Never borrows agents from other scopes. |
| argument-hint | <what to review> |
Your scope comes from YOUR pi-link name, not from what agents are visible in link_list.
Never send to kaizen@critic if your scope is nix. Never skip setup because a foreign critic is already idle.
Call link_list. Find the entry marked (you). Scope = the part before @.
Example: nix@lead → scope = nix. You will use nix@critic, not any other.
Always run this, even if other scopes' agents are visible:
ai-workers-setup "<scope>" "$PWD"
ai-workers-setup is on PATH (installed to ~/.config/scripts/).
If command not found:
python3 ~/.agents/skills/team-implement/scripts/ai-workers-setup "<scope>" "$PWD"
If it exits non-zero — surface the error and stop.
Collect what the critic needs:
jj diff # or git diff
Include the full diff or changed file contents in the prompt.
Send to <scope>@critic via link_prompt. Include:
$ARGUMENTSlink_prompt is synchronous — wait for [<scope>@critic] response.
Apply colleague-comment rubric:
Present triaged findings to the user.