القائمة
Review a diff against a task's success criteria. Use when: a `task_assignment` for role `reviewer` lands; you need to lint, summarize a diff, or produce structured review comments.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Validate and fact-check another agent's output against evidence and the task's success criteria. Use when: verifying a report, fact-checking claims, cross-checking research findings, confirming a result meets its criteria. Not for browser/E2E testing (see e2e-runner).
Procedure the Researcher agent follows to answer a question with web search + page fetch: plan queries, search, open the promising pages, cross-check, and return a source-cited synthesis. Use when a task needs current or external facts.
Example skill scaffold. Replace this with a real, project-specific procedural playbook. The description must clearly state WHEN to use the skill (trigger phrases and scope) so the model can match it to user intent. USE FOR: <list the situations this skill applies to>. DO NOT USE FOR: <list out-of-scope situations and point to the right skill>.
The Planner's operating procedure. Use when: turning a principal goal into a Plan; revising a plan after rejection; dispatching ratified tasks; supervising sub-agent results; deciding whether to convene the Council; finalizing a run.
Classify a proposed action's risk tier (T0–T4), apply the gate policy, and (if required) summarize the proposal into a human-reviewable approval request. Use whenever an agent is about to perform an action that touches anything outside its own scratch state.
Append a structured event to the run's provenance log. Every agent calls this for every meaningful state transition (plan drafted, task dispatched, action proposed/executed, approval decided, etc.) so the run is fully replayable and auditable.
| name | reviewer-runner |
| description | Review a diff against a task's success criteria. Use when: a `task_assignment` for role `reviewer` lands; you need to lint, summarize a diff, or produce structured review comments. |
| argument-hint | Path to the task_assignment message; the message payload should reference the diff path. |
task_assignment for role reviewer.successCriteria to review against.reviewer.agent.md.shared/approval-gate/SKILL.md and
shared/provenance/SKILL.md.assigneeRole === "reviewer" and the
inputs.diffPath points at an existing artifact.task_started.eslint, ruff, golangci-lint, etc.).
Capture output under runs/<runId>/artifacts/<task-id>/lint.log.successCriteria.runs/<runId>/artifacts/<task-id>/review.md with two sections:
file:line and the criterion it violates.comment:pr capability) if the diff is a real PR.
Otherwise the artifact is the deliverable.TaskResult:
success if Blocking is empty and lint is clean.partial if lint has warnings but no errors and no Blocking items.failure if any Blocking item or any lint error.task_result and message the Planner.🚧 Scaffold.