Communitygithub.com

video-review-and-delivery

The loop that turns a built film into a delivered one. Look at frames, measure sound, run checks, show drafts and samples to the person, act on their feedback, render the master, verify the finished file, write the project record, and report. Use after any build or change, before every render, and whenever feedback arrives.

What is video-review-and-delivery?

video-review-and-delivery is a Claude Code agent skill that the loop that turns a built film into a delivered one. Look at frames, measure sound, run checks, show drafts and samples to the person, act on their feedback, render the master, verify the finished file, write the project record, and report. Use after any build or change, before every render, and whenever feedback arrives.

Works with~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/shubhamnshukla/video-agent-kit/tree/main/skills/video-review-and-delivery

Ask in your favorite AI

Open a new chat with this agent skill pre-loaded.

Documentation

Review and delivery

1. The loop after every change

  1. npx hyperframes lint. Zero errors.
  2. npx hyperframes snapshot --at 3.4,7.8,35.2,... at the moments you changed, plus one before and one after. Open the contact sheet and actually read it: is every card complete, is any face covered, does any text run out of its box, is anything half-drawn that should be finished?
  3. Fix and repeat until the frames are right.
  4. npx hyperframes check --json (or scripts/check.sh with 4K footage). Fix errors. Read the warnings once and decide: fix it, or keep it and say why in REVIEW.md. Warnings worth acting on: nothing changing for more than three seconds, an empty first frame, text running out of a container.

Snapshots are cheap; renders are not. Do all the looking you can before rendering.

2. Drafts

A draft is the whole film at low quality: npx hyperframes render --quality draft -o renders/draft-01.mp4, one to three minutes for a 100-second film at 1080p. Then:

  • Make a sheet of the rendered file (scripts/sheet.sh renders/draft-01.mp4 sheet.jpg 1/2.6 8x5) and read it. It shows the film as encoded, including footage, which snapshots can get wrong.
  • Measure loudness: ffmpeg -i draft.mp4 -af ebur128=peak=true -f null -.
  • Measure the level every two seconds (scripts/levels.py draft.mp4 2) and compare it with the plan: is the quiet part quiet, does the lift arrive where the product does?

Give the person the draft with a short note of what is in it and what you want their eye and ear on. The first draft exists to be corrected; get it to them early rather than polished.

3. Showing options

When the question is a look (a highlight style, a font, a layout, a colour), show stills, not renders.

  • Build each option, snapshot the same three or four moments, and save the contact sheets side by side with plain names (A-underline.jpg, B-band.jpg).
  • Say in one line each what A and B are, and which you would choose and why.
  • Wait for the answer only on this point; keep working on everything that does not depend on it.

When their words could mean two things, this is how you find out. It costs a minute. A wrong full render costs ten and their patience.

4. Acting on feedback

Feedback arrives short, informal and sometimes annoyed. Handle it like this:

  • Restate it as an action before acting, in a line: "Singapore photo: same small print as the others, in the problem and the ending."
  • Apply it everywhere it applies. If one element was wrong, its siblings elsewhere in the film are wrong the same way.
  • Take taste as given. "Slow", "boring", "looks cheap", "too thick": change it; do not defend it. If you disagree on a point of fact (it would hide a face, a claim would be untrue), say so once, with the reason.
  • Common notes and what they mean:
They sayDo
slow, sleepy, boringshorter shots, faster voice, cut lines, more energetic music; not more effects
doesn't look real, looks AIreal footage of real people; fewer invented graphics
looks like stock clips stuck togetherone grade on everything; recurring people; consistent cards
I can't connect with itnames, jobs, specific wants; the problem in their own words
the sound is flat, one wayscore it by mood; quiet before the lift
make it catchyrewrite the hook and the summing-up line; add a callback
this one is different from the othersmake it match its siblings exactly
more attention on these wordsone emphasis mark per line, shown as stills first
  • Several messages at once: deal with each; say in a line how. A later message overrides an earlier one.
  • Record decisions in REVIEW.md and in memory: what they chose, what they rejected, in their words.

5. The master render

When the draft is approved or the remaining changes are small:

  1. Check free disk space. A 4K render needs about 11 GB of temporary space per 100 seconds.
  2. npx hyperframes render --quality delivery --resolution landscape-4k -o renders/<name>-4k.mp4, in the background. Add --gpu if they want speed or asked for it; say what it costs (about half the bitrate).
  3. If they ask how long, read the render's progress and answer with a number.

Name versions plainly (-v2, -v3). When a version is rejected, delete it so nobody opens it by mistake.

6. Verify the finished file

Do this on the file you are about to hand over, not on the project.

  • ffprobe: resolution, frame rate, duration, size.
  • A sheet of the whole file: every section present, no blank or frozen stretch, the last frame correct.
  • A full-size crop of text and of a face: sharp type, footage not blocky.
  • Loudness: about −16 LUFS integrated, true peak at or under −1 dBFS.
  • The QR code decoded from a late frame (scripts/scan.py): the exact link, at full and half size.
  • The address on the end card answers when requested.

7. The project record

Update the four files before reporting. templates/ has each one as a skeleton.

  • SCRIPT.md: the script table (time, picture, voice), the people, where each line comes from, the numbers.
  • SPEC.md: goal, output, timing and sound plan, look, type, motion, the shot list with frames, a QA list.
  • CREDITS.md: every source and its licence.
  • REVIEW.md: calls made; measured, looked at, not checked; open decisions; weakest shots; warnings kept on purpose; how to change the film (which file, which command).

8. The hand-over message

Short, in this order:

  1. The file: path, resolution, length, size.
  2. What changed since the last version, as a short list.
  3. What you checked and how; what you did not (you never heard it).
  4. What needs their decision, most important first: things not live in the product, anything on screen the company might not want shown, licences to confirm, pronunciations to listen for.

No adjectives about your own work. If something failed or is missing, that is the first line.

9. Housekeeping

  • Keep the source downloads and manifests the film is cut from; delete candidates you did not use, old drafts and caches when space is short or when asked. Look at what you are about to delete; delete only what you made.
  • Never commit or push their repository unless asked.
  • Keep generator scripts and helper scripts in the project, not in a temporary folder that a restart clears.

Individual skills in this repo

This repo contains 3 individual skills — each has its own dedicated page.

Related Skills