Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From harness-flow
Routes a review request to the appropriate HarnessFlow review node (discovery, spec, design, ui, tasks, test, code, traceability) based on artifact context. Returns a verdict and reviewer contract.
npx claudepluginhub hujianbest/harness-flow --plugin harness-flowHow this command is triggered — by the user, by Claude, or both
Slash command
/harness-flow:reviewThe summary Claude sees in its command listing — used to decide when to auto-load this command
Bias toward HarnessFlow's review nodes. There is **no single "review" skill** — review responsibility is intentionally split across independent nodes (Fagan-style separation), and the router decides which one to dispatch through `hf-reviewer`. Steps: 1. Enter via `skills/using-hf-workflow/SKILL.md` and hand off to `skills/hf-workflow-router/SKILL.md`. 2. Tell the router that the user's intent is "review request" and pass any specific artifact target the user mentioned (e.g. "review the spec", "review TASK-003 code"). 3. The router consults `skills/hf-workflow-router/references/review-disp...
/reviewDispatches expert reviewer agent to critique workflow artifacts like roadmaps, steps, or implementations, producing structured Radical Candor feedback and approval verdict.
/run-review-loopInvokes the review-loop:review-loop skill and executes its instructions exactly as presented, following the provided playbook.
/reviewPerforms final code quality review and security audit before deploy, producing approval/rejection report with prioritized findings.
/auditLoads and executes Hypo-Workflow audit skill instructions, applying structured review with user-provided arguments.
/flow-reviewDispatches code review subagent for a flow ID: derives git range from Beads tasks or fallback, reviews against spec/patterns, outputs severity-based findings and logs summary.
/fire-7-reviewPerforms multi-perspective code review using 16 specialized reviewer personas on files, directories, PRs, or phases, producing a detailed report.
Share bugs, ideas, or general feedback.
Bias toward HarnessFlow's review nodes. There is no single "review" skill — review responsibility is intentionally split across independent nodes (Fagan-style separation), and the router decides which one to dispatch through hf-reviewer.
Steps:
skills/using-hf-workflow/SKILL.md and hand off to skills/hf-workflow-router/SKILL.md.skills/hf-workflow-router/references/review-dispatch-protocol.md and dispatches agents/hf-reviewer.md to one of:
skills/hf-discovery-review/SKILL.mdskills/hf-spec-review/SKILL.mdskills/hf-design-review/SKILL.mdskills/hf-ui-review/SKILL.mdskills/hf-tasks-review/SKILL.mdskills/hf-test-review/SKILL.mdskills/hf-code-review/SKILL.mdskills/hf-traceability-review/SKILL.mdhf-reviewer runs as an independent author/reviewer separation role; do not let it edit the artifact under review.Hard rule: review nodes return a verdict + reviewer return contract; the router (not this command) decides what happens next based on that verdict.
The user request following this command should describe what needs reviewing.