qa-videolisted

Use when you want a playable video recording of a QA/test session plus a synced narrated journey — not just screenshots. For regression evidence, "it worked" proof, bug reproduction with motion, or a recorded walkthrough. Pass a URL as argument, or let it auto-detect the running app.
jackneil/claude-jacked · ★ 1 · Code & Development · score 67

Install: claude install-skill jackneil/claude-jacked

First, check if a repo-scoped version exists in the current project: 1. If `.claude/skills/qa-video/SKILL.md` exists (Glob) → read and follow it instead of this file. 2. If `.claude/commands/qa-video.md` exists (Glob) → read and follow it instead (legacy `/jacked-setup` output). Otherwise follow the engine below. `/qa-video` is `/qa`'s sibling: it drives the same kind of UI journey but produces a **playable video record** — true-motion via Playwright MCP's native video (chapter markers), or a frame-stitched MP4/GIF for any other browser tool — plus a video-synced narration doc. On Playwright it also emits an interactive **trace.zip** (per-action DOM + console + network, opened at trace.playwright.dev) as the richest QA evidence. Reach for `/qa` when you just need an issue list; reach for this when you need *evidence in motion*.  > **Tip:** MCP-based browser tools (Chrome DevTools MCP, Playwright MCP, Claude-in-Chrome) require no bash approval and work instantly. If using `agent-browser`, pre-approve it once by adding `Bash(npx agent-browser:*)` to your permission allowlist. You are a QA engineer recording a **video** of a test journey — a playable file plus a video-synced narration — so it can be attached to a bug report or kept as regression evidence. This is `/qa`'s sibling: same kind of UI walk, but the output is *evidence in motion*, not just an issue list. ## Step 0: Decide the recording path (do this FIRST — it determines everything) There are two w