review-loop
Skill0 starsChanged 5 days agoMITView on GitHub
Review a rendered video like a strict director before showing it to anyone, using contact sheets, a phone-size test, the first frame, loudness and a fix-the-worst-3 loop. Use after every render.
54 other projects use a version of this.
Adopted by
Most recently taken up by
- revisit-studies/studytheir own version, first seen Nov 9, 2026
- zane-tv/holdframetheir own version, first seen Nov 8, 2026
- seankoji-com/.agentstheir own version, first seen Nov 8, 2026
- BK202503/open-claude-alltheir own version, first seen Nov 8, 2026
- Latand/delegatustheir own version, first seen Nov 8, 2026
- blockscout/frontendtheir own version, first seen Nov 1, 2026
Used with
Projects with it also use polish, to-spec and 9 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
HK-hubSkillpolish
Performs a final quality pass fixing alignment, spacing, consistency, and micro-detail issues before shipping. Use when the user mentions polish, finishing touches, pre-launch review, something looks off, or wants to go from good to great.
Also in 3 projects that use this
GoogleSkillto-spec
Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.
Also in 4 projects that use this
- GoogleSkill
improve-codebase-architecture
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
Also in 5 projects that use this
AWSSkillship
Finalize dev work on an issue branch — update docs, push, and open a PR.
Also in 4 projects that use this
MicrosoftSkillcouncil
Convene the persona panel — six orthogonal review lenses — on a target. Cold independent fan-out, debate-to-consensus, synthesized verdict with recorded dissent and a roster manifest.
Also in 3 projects that use this
SentrySkillreview
Fixture review skill.
Also in 5 projects that use this
- +4 more from google
Other versions54 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 54
- didi/mpx★ 4ksame name
- blockscout/frontend★ 310same name
- microsoft/bocpy★ 184same name
- 9thLevelSoftware/legion★ 76same name
- microsoft/Trieste★ 53same name
- revisit-studies/study★ 46same name
- timharris707/skills★ 44same name
- Latand/delegatus★ 37same name
- spxrogers/agentsync★ 35same name
- mathruffian-dot/claude-motion-explainer★ 30same name
44 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository6 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- cartoon-studioSkill
- motion-designSkill
- promo-reelSkill
- talking-head-editSkill
- word-captionsSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 47 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 28
Write each fix as WHERE (frames) / PROBLEM / CHANGE / KEEP so nothing else moves.
“Common” is measured: kept by at least 6 in 10 of the 47 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Review Loop
1. Make the frames come to you
bash scripts/check_export.sh path/to/video.mp4
ffmpeg -hide_banner -i path/to/video.mp4 -af ebur128=framelog=quiet -f null - 2>&1 | grep -A2 IntegratedOpen *_contact.png (1 fps), *_phone.png (360 px wide) and *_first_frame.png.
2. Critic pass
You did not make this video. Check:
- Spec: 1080x1920, 30/1 fps, planned duration; loudness around -14 LUFS.
- First frame: content visible (it is the cover on mobile). No black intro, no white flash.
- Readability at phone size: captions and key numbers readable at 360 px wide.
- Safe areas: nothing important in the bottom ~250 px or right ~120 px (platform UI).
- Overlays never cover the face or the captions.
- Text: no overflow, no wrong casing, no misheard words, no banned phrases (brand JSON).
- Facts: every number, price and term matches the source.
- Motion: no linear spatial moves, nothing static for more than ~3 sec without a new idea.
3. Fix the worst 3, repeat
List every problem with a timestamp. Fix the three worst, re-render (use npx remotion still … --frame=<n> for single-frame checks), and repeat until the list is empty or only taste notes remain.
Write each fix as WHERE (frames) / PROBLEM / CHANGE / KEEP so nothing else moves.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.