video-bug-analysislisted

# Video Bug Analysis You can't watch video — only **still frames** `ffmpeg` extracts. Reconstruct what happened from those snapshots plus what the user tells you. Despite the name, this also handles **non-bug "read the screen" tasks** — inventorying a site's features, transcribing a demo, or describing on-screen UI from a recording. Work this way: > **Reading dense text/UI (not a bug)?** Skip the contact sheet — extract **full-resolution > individual frames** (`--fps 1` to `2`, no `--contact`) and read them one by one. Contact > tiles downscale too far for small text, especially on tall **portrait** phone captures > (where the script auto-drops to `--cols 2`, but individual frames still read best). ## 1. Get context first Ask for whatever's missing: - **When** the bug appears (a timestamp/range like "~0:12") — the biggest accuracy lever. - **Repro steps** and **expected vs. actual**. - **Console / network / logs** — invisible in the video unless devtools are on screen, and often the real cause. - **Relevant code area**, if known. A **still screenshot of the bad moment** beats hunting inside a clip — **prefer it, and ask for one** whenever a timestamp is fuzzy or ffmpeg isn't available (see the ffmpeg note below). ## 2. Extract frames ``` ${CLAUDE_PLUGIN_ROOT}/skills/video-bug-analysis/scripts/extract-frames.sh \ --video <path> [--fps <n>] [--scene <thr>] [--contact] [--timestamps <t1,t2>] ``` Default workflow: 1. **Overview:** `--fps 2 --contact` → one contact s