Communitygithub.com

DomCamillo2/VideoEditting

Prepare a reviewable preview, verify the final encoded video and hand off a versioned editing project. Use before export or when diagnosing black borders, crop errors, missing assets, drift, color or audio problems; do not claim creative QA from a successful build alone.

O que é VideoEditting?

VideoEditting is a Claude Code agent skill that prepare a reviewable preview, verify the final encoded video and hand off a versioned editing project. Use before export or when diagnosing black borders, crop errors, missing assets, drift, color or audio problems; do not claim creative QA from a successful build alone.

Funciona com~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/DomCamillo2/VideoEditting/tree/HEAD/.agents/skills/video-export-qa

Perguntar na sua IA favorita

Abre um novo chat com esta habilidade de agente já pré-carregada.

Documentação

Verify the file the user will watch

Read the brief and intended deliverable. A small fix needs checks proportional to the change, not a compulsory new approval ceremony. Preserve earlier versions and original media.

Before the long render

  • Check source dimensions, rotation, fps/time bases, variable-frame-rate behavior and audio synchronization. Choose target fps from the brief/material; don't impose 30 fps on every project. Relink proxies to correct originals and inspect source in/out points.
  • Confirm aspect ratio, resolution, codec and color pipeline. Mixed HDR/SDR needs explicit handling and test encodes; keep skin/highlights stable across cuts. Do not label an SDR export HDR. Compare adjacent exposure and white balance before applying a heavy look.
  • Validate media references against the project root before rendering: files must exist and symlinks must not escape the intended media scope. Keep explicit source in/out (exclusive end), source fps, timeline fps and constant playback rate; compare mapped duration to the chosen shot length. Unknown source ranges stay unknown. A file-existence check does not measure available frames or certify decode quality.
  • Render a small representative sample including a portrait/group, fast action, dark scene, transition, gag if selected, song change, speech and ending. Inspect actual frames and movement. A web player or TypeScript build alone is not an encoded-video test.

Full preview and master

  1. Review chronology/chapter labels, repeated shots, emotional pacing, unwanted gags and ending. Check no fabricated route or embarrassing selection slipped in. Keep key people/gestures clear of text and effects.
  2. Review protected portrait crops at start/middle/end and motion extremes; look for black/transparent edges, stretching, desynchronized blurred backgrounds and cutout halos. Check anchors through movement and occlusion. For stabilized clips, compare the corrected motion with the original at playback speed. Check worst jolts for lost heads/hands/feet, wobbling geometry, edge fills, zoom pumping and blur; verify duration, frame mapping, audio sync and any tracking rebuilt after stabilization. Bind approval to the corrected derivative's hash and reviewed intervals.
  3. Review audible beat accents and dialogue ducking. Count marker alignment separately from actual listening. Check source-to-timeline offsets after transitions and speed changes.
  4. If captions are requested, verify words/timing, readable duration, contrast, line breaks and placement against faces and destination UI. Review strong flashes or excessive shake and soften unnecessary ones.
  5. Render a new version and fully decode the actual file. Inspect codec, resolution, fps, duration/frame count, audio streams and missing-media indications. Measure black intervals, silence, loudness and true peaks if tools are available; classify intentional darkness/silence manually.
  6. Bind QA to version, file hash and time. Inspect representative frames from that final encode, plus changed risky ranges. Don't reuse an old preview's passed label after a new render. Run a full re-review only when changed scope or unresolved concerns require it.

Handoff

Provide the actual playable export path, editable project, relative media/music manifest, selection/exclusion reasons, routes if used, beat/effect cue lists and remaining issues. Distinguish preview from final and state missing dependencies. Use clear statuses: measured, visually reviewed, listened, not checked; never claim viewing/hearing you did not perform. Publishing private source material needs current user authorization, not this skill.

Individual skills in this repo

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

DomCamillo2/VideoEditting

Mix music, dialogue, authentic location sound and comedic sound effects for an edit. Use for ducking, song transitions, J/L cuts, intelligibility and clean endings; not as a substitute for beat detection or actual listening.

DomCamillo2/VideoEditting

Cut photos or video on audible musical beats, downbeats and phrase changes, or diagnose an edit that feels off beat. Use for music-led timing and transitions; do not equate waveform peaks or automatic markers with verified musical accents.

DomCamillo2/VideoEditting

Establish a film or reel brief, including tone, humor, travel type, route and relevant vehicle details. Use when these choices are missing or the user changes direction; skip for a small revision with an established brief.

DomCamillo2/VideoEditting

Reconstruct capture order, trip chapters and road/ferry map segments from photo/video metadata and visible evidence. Use when travel chronology or route labels matter; do not invent exact dates or transport links from filenames alone.

DomCamillo2/VideoEditting

Add playful video gags such as person cutouts, spins, loading effects, face-zoom transitions or tracked scooter flames. Use when humor is requested in the current brief; do not add unsolicited meme edits to a serious film.

DomCamillo2/VideoEditting

Fit portrait photos or videos into landscape edits, or reframe mixed aspect ratios with a blurred copy of the same media. Use to prevent black borders and cropped faces or bodies; not for privacy anonymization or sharpening a blurry subject.

DomCamillo2/VideoEditting

Cull and rank photos or video excerpts, remove repetitive selections, and compare blurry versus sharp takes. Use for bursts, near-duplicates, contact sheets and best-moment selection; never delete source media or judge focus only from a blurred background.

DomCamillo2/VideoEditting

Onboard a new user to the VideoEditting toolkit by choosing all or selected editing skills, assessing useful MCP integrations and setting up approved tools before the film brief. Use for first-time adoption or setup changes, not every editing revision or repository maintenance task.

Habilidades Relacionadas