vidhi-reviewlisted

# Task Review Review code changes scoped to one or more yojana tasks. Lighter than vidhi-release-review — no pack, no parallel subagents, no full code-intel sweep. The reviewer focuses on whether *this change* is correct, clean, and consistent with the task's acceptance criteria and the project's contracts. ## When to use - After completing a task or set of related tasks, before moving on - When you want a second opinion from another model (codex, opencode, glm) - When reviewing someone else's work against a yojana task spec ## When NOT to use - **Whole-project audit** — use vidhi-release-review. It builds a full pack with code-intel and runs parallel architecture + review passes. - **Architecture improvement** — use vidhi-deepen. This skill checks what's there, not what could be better. - **Bug investigation** — use vidhi-diagnose. Don't use review to find the bug; review checks whether the fix is right. ## Entry Accepts one or more yojana task IDs: `vidhi-review chitta/32` or `vidhi-review chitta/32 chitta/33 chitta/34`. If no task IDs are given, ask the user. Don't guess from git state. ## Process ### 1. Gather task context For each task ID: ``` yojana_context task="<id>" shape="review" ``` This returns: description, acceptance criteria, decisions, implementation plan, git/doc context_refs, and neighbor summaries. Collect the set of acceptance criteria across all tasks — these are the spec the reviewer checks against. ### 2. Determine the diff The diff is t