vawe-review-loop

Iterates render, judge, and critic passes on a rendered film until a written stopping rule ends review.

3|Updated Jun 9, 2026
One-click install
npx skills add https://github.com/Vandit1604/vawe --skill vawe-review-loop-vandit1604
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vawe-review-loop
Source: https://github.com/Vandit1604/vawe/tree/main/skills/vawe-review-loop
Command: npx skills add https://github.com/Vandit1604/vawe --skill vawe-review-loop-vandit1604

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Rendered films that pass structural gates can still be visually weak, and review sessions typically end when the author loses patience rather than when quality stops improving. This Skill wraps the existing gates, judge sheets, and critic roster into one loop with an explicit stopping rule so review ends on evidence. ## Core Features & Use Cases - Structured review rounds: Runs make ship, make judge, make beats, and make reveal per round, then scores every frame on seven dimensions (readability, hierarchy, composition, brand fidelity, asset fidelity, produced-not-generated, value). - Independent verdicts: Requires a separate critic subagent to confirm a PASS verdict, preventing the author from self-certifying their own film. - Written stopping rule: Stops after two consecutive finding-free rounds, when fixes stop raising the lowest score, or at round five with a concept-level diagnosis; includes regression and gate-is-wrong guards. - Use Case: After rendering a scene JSON to video, run the loop to catch unreadable captions, flashing seams, focal-point-free beats, and type-only frames before shipping the film. ## Quick Start Review the film I just rendered from films/scene/my-film.json and keep fixing it until the stopping rule says it is done.

Frequently Asked Questions about vawe-review-loop

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a rendered video film for quality issues?

Run one loop round with make ship, make judge, make beats, and make reveal on the scene JSON, then read the generated sheets and score each frame on the seven rubric dimensions. Write the issue and fix for anything scoring 3 or below, then repeat until the stopping rule fires.

How to know when a video review loop should stop?

Stop when two consecutive rounds produce no new finding scoring 3 or below, when a round's fixes fail to raise the lowest dimension score, or at round five, which indicates a concept-level problem. Anything else means continue iterating.

Why do passing gates not guarantee a good rendered film?

Structural gates like make author-check only verify the film is not broken; they cannot detect murk, weak focal points, or frames that are just type on a background. Perceptual review via make judge, critics, and direct frame inspection is required above that floor.

Can the film's author record the final PASS verdict?

No. The author's own read of make judge is biased toward passing, so the judge sheet and rubric must go to a separate critic subagent that did not author the film. PASS is recorded only when that independent eye agrees.

When should I not run the full review loop?

Skip the loop for one-line tweaks, caption typos, or color swaps verifiable in a single frame; run make dev and look instead. The loop is for full passes, recreations, or anything going in front of other people.