← ClaudeAtlas

vidhi-release-reviewlisted

Run a thorough, multi-pass code review of a project at a release or checkpoint moment. Use when the user wants to verify a project is ready to ship, audit a long upgrade arc, or get fresh-eyes review on accumulated changes. Different from vidhi-deepen (forward-looking refactor candidates) and per-task PR review (which uses yojana_context shape="review" directly).
ninthhousestudios/vidhi · ★ 0 · Code & Development · score 72
Install: claude install-skill ninthhousestudios/vidhi
# Release Review A two-pass review for a project at a release or checkpoint moment. Designed so the same review pack is also the input for external models (codex, glm, others) — no Claude-specific tooling lives in the pack. ## When to use - Before tagging a version - Mid-stream during a long upgrade arc (checkpoint review — substitute the verdict, see Severity below) - Before handing a project to other reviewers (e.g. external models) ## When NOT to use - **Per-task PR review** — call `yojana_context shape="review"` for the task plus the diff. Different, lighter-weight workflow. The release review's pack is overkill for a single task. - **Forward-looking refactor planning** — use vidhi-deepen instead. (Release review *spawns* vidhi-deepen as one of its two passes — see step 5.) - **Cross-project consistency for the manas constellation** — wait for vidhi-constellation-review (TBD). ## Process ### 1. Verify project state - `git status --short` — uncommitted work in the diff makes the review noisy. If dirty, ask the user whether to stash or include. - Confirm scope with the user: tagged release, commit range (e.g. `wm-1..wm-12`), or all-of-HEAD? - Note in `00-meta.md` whether this is a release gate or a checkpoint. - Check whether a running daemon's version matches the source version — they may differ during a deploy gap. Record both in meta. ### 2. Build the review pack Pack location: `/tmp/review-pack-<project>-<date>/` (transient — pack is reproducible from source).