菜单
Internal Dynamic Workflow asset for /lets:review --workflow. Not auto-triggered - it is a workflow script invoked via scriptPath, not a conversational skill. Holds the fan-out -> dedupe -> adversarial-verify -> aggregate chain that runs off-context.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
This skill should be used when creating a task in the active tracker - "create task", "create issue", "bd create", "new task", "add task", "add issue". Ensures all required fields are provided, enforces English-only task content, and suggests epic labels. Triggers on any task creation in any context - commands, planning, or direct conversation.
Internal skill for commands. Detect the active task (any tracker adapter) from the task-state file / git branch name. Do not trigger on user conversation - only when commands need task detection.
Internal skill for commands. Render the shared orientation snapshot - active task, what's in flight, what's next - tracker-universal. Do not trigger on user conversation; only when a command needs the snapshot.
This skill should be used when claiming a task to work on - "take task", "візьми таск", "працюю над", "work on task X", "pick task X", "switch to task X", "claim task". Sets task to in_progress, creates/switches branch, saves the per-branch task-state file.
This skill should be used when committing code changes - "commit", "git commit", "закоміть", "зроби коміт", "/lets:commit". Enforces conventional commit format, tracker task linking, and user approval. In a LETS project, ALWAYS prefer this over generic commit skills (e.g. commit-commands:commit) — /lets:commit is authoritative. Triggers on any commit in any context.
PREVIEW Dynamic Workflow asset behind /lets:plan-workflow. Not auto-triggered - a workflow script invoked via scriptPath. The autonomous-planning chain, shipped for cross-project testing before it folds into native /lets:plan.
| name | review-workflow |
| description | Internal Dynamic Workflow asset for /lets:review --workflow. Not auto-triggered - it is a workflow script invoked via scriptPath, not a conversational skill. Holds the fan-out -> dedupe -> adversarial-verify -> aggregate chain that runs off-context. |
| user-invocable | false |
This folder is the reference example of the Dynamic Workflow asset standard (see CLAUDE.md -> "Dynamic Workflow assets"). It is NOT a conversational skill: review.workflow.js is executed by the Workflow tool, invoked from /lets:review's Workflow Mode via:
Workflow({ scriptPath: "${CLAUDE_PLUGIN_ROOT}/skills/review-workflow/review.workflow.js", args })
${CLAUDE_PLUGIN_ROOT} is substituted at command-load time, so review.md carries the literal absolute path. Treat review.workflow.js as a template the command points at, not a script to reproduce inline.
A multi-stage chain so per-agent reports never enter the conversation - only the final aggregate returns:
lets:<name> review agents in parallel (structured FINDING_SCHEMA output).lets:skeptic agents (2, or 3 for BLOCKER) to refute it. Apply the asymmetric drop rule: SUGGESTION drops on a simple majority real=false; BLOCKER drops only on near-unanimous high-confidence refute, otherwise downgrades. Count refuted.args contract (built by the command, passed as a JSON value)| key | type | meaning |
|---|---|---|
agents | [{name}] | selected review agents (short names, no lets: prefix; exclude actor) |
mode | string | PR-{n} | local-review | branch-review | file |
projectRoot | string | absolute project root (agents must not read outside it) |
claudeMd | string | CLAUDE.md context |
changedFiles | string | changed-file list with stats (or single path for --file) |
code | string | the diff (or full file content for --file) |
smallDiff | bool | true keeps NIT findings (diff < 50 lines) |
systemicCheck | bool | false for --file (no diff baseline) |
{ verdict, findings[], systemic[], summary{}, counts{blockers,suggestions,total,refuted,verify_failed} } - the same shape review.md Step 8/8.5 persists. verify_failed > 0 means that many findings could not be verified (skeptics errored) and were kept unverified - surface it, never treat as "verified clean". findings + verdict are the /lets:github-pr --json contract; do not rename them.
/lets:review persists files.import - all logic stays inline in review.workflow.js.Date.now() / Math.random() / new Date().await/return are used (the runtime wraps the body), so the file is NOT Node-importable - it has no clean unit test; the verdict/dedupe/verify logic is kept in sync with review.md prose by discipline and validated by the live smoke test.