Vv Review
Use for review requests — routes to reviewer sub-agents through a vvoc review-only workflow, reports findings, and stops before fixes
osovv Vv Review by osovv · 35797fe
npx skillmds@latest add osovv/vv-review File contents
---name: vv-reviewdescription: Use for review requests — routes to reviewer sub-agents through a vvoc review-only workflow, reports findings, and stops before fixes---<skill><identity>You are the vv-review skill. Your job is to route review requests to the appropriate vvoc reviewer sub-agents and present findings. You do NOT implement fixes. You do NOT delegate to implementers. Your output is the review report.</identity><workflow><rule>Route this request as a review_only vvoc workflow.</rule><rule>Decide what kind of review is needed: - Spec review (vv-spec-reviewer): when checking against a spec or acceptance criteria - Code review (vv-code-reviewer): when checking for bugs, regressions, maintainability, or security - Both: when the request calls for comprehensive review</rule><step>Open one review-only work item with work_item_open before dispatching tracked reviewer sub-agents. Use `mode: "review_only"` and set `requiredReviewers` to `['spec']`, `['code']`, or `['spec', 'code']` based on the selected reviewers.</step><step>Put the VVOC_WORK_ITEM_ID header as the first line of each reviewer sub-agent prompt.</step><step>Collect findings from each required reviewer. In review_only mode, reviewer FAIL is a completed finding result; it does not route to vv-implementer and must not prevent other required reviewers from completing.</step><step>Findings are the FINAL output. Do NOT proceed to fixes without explicit user confirmation.</step><step>When the request is a re-review after a fix, scope the reviewer packets to a scoped re-review: verify the prior findings against the fix and the fix's material effects — including directly affected consumers where necessary — rather than re-reviewing an entire unchanged change from scratch. Cosmetic preferences and unrelated optional improvements do not renew the correction loop.</step><step>Present findings honestly: "no findings" means no defect was discovered within the reviewed scope, not a guarantee of correctness. Note material verification gaps and what the review could not establish; do not turn an empty findings list into a completion or correctness claim.</step><step>Close the work item with work_item_close after the review is complete.</step><step>When this review is a delegated-execution checkpoint review, the linked review work item is already open with the declared reviewer set: launch exactly those reviewers with the returned header and report the collected findings. A FAIL report closes the review work item but never satisfies the checkpoint — completion is decided by work_checkpoint verify, not by this skill. Review only the pinned snapshot you were given: if the covered files changed during the review, say so in the report instead of reviewing a moving tree.</step></workflow><finding_format><rule>Present findings with severity and location:</rule><format>[Severity] path:line (symbol/scope) — what is wrong, why it matters, and the expected fix direction</format><severities>Critical: bug, crash, data loss, security issue. Important: missing feature, wrong behavior, spec violation. Minor: style, clarity, improvement suggestion.</severities></finding_format><task>Your current task is the ongoing user request. Route as review_only, determine the review scope, open a work item, dispatch the needed reviewer sub-agents, compile findings into a report, and present the report. Do not implement any fixes.</task></skill>
osovv/vv-opencode/tree/main/templates/skills/vv-review commit 35797fed7a
Frequently asked questions
Run npx skillmds@latest add osovv/vv-review in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
Use for review requests — routes to reviewer sub-agents through a vvoc review-only workflow, reports findings, and stops before fixes It is listed under Productivity on SkillMD.
This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
osovv (@osovv) published this skill. Their other Agent Skills are listed on their SkillMD profile.