review-pack

# review-pack ## Overview A structured self-review and user sign-off. The skill: 1. Re-reads the spec and the plan. 2. Reads the full diff from the isolation base to HEAD on the vibe branch. 3. Critiques its own work against the spec (not against abstract best practice — against *this* spec). 4. Presents a severity-ranked list of findings + the full diff + a sign-off prompt. 5. Waits for user approval before handing off. This is the last reasoning gate before the pipeline touches anything outside the isolated workspace. ## When to invoke - After `verify-gate` returns verdict `ready`. - `security-review` is a complementary optional gate (threat-model, not spec-conformance). Either or both may run after `verify-gate` and before `finish-branch`; there is no ordering dependency between them. - Before `finish-branch`, before any merge, PR, push, tag, or deploy. - When the user explicitly asks for a review of completed work. Do not invoke: - If `verify-gate` returned `not ready`. Review-pack is not a bypass. - If no commits exist on the vibe branch beyond the base — there is nothing to review. ## Prerequisites - Spec exists at the path recorded by the vibe run, `status: approved` in frontmatter. - Plan exists at the path recorded by the vibe run. - Verify-gate report exists with `verdict: ready`. - Vibe branch has at least one commit beyond the isolation base. If any prerequisite fails, stop and surface what is missing. ## Self-review procedure (Reflexion) Run through t...