← ClaudeAtlas

review-handofflisted

Use when Pedro wants a Symphony human-review handoff artifact for a UI fix, especially a slower browser video that clearly shows the relevant behavior using existing auth/setup helpers instead of a full test-suite style demo.
PedroAVJ/swe-stack · ★ 0 · Code & Development · score 73
Install: claude install-skill PedroAVJ/swe-stack
# Symphony Review Handoff Create human-readable review artifacts for UI changes. Prefer short, focused browser recordings or screenshots over fast regression-test videos. ## When to use Use this skill when the user asks for: - a handoff video - a review video - a slower demo for humans - a clear visual proof of a fix This skill is for demonstration, not broad regression coverage. The review unit is the user-facing issue or bug, not the branch or PR. ## Core rules 1. Reuse existing auth/setup helpers when the repo already has them. 2. When the repo already has Playwright config, global setup, fixtures, storage state, or passing specs for the target flow, build the handoff artifact on top of that existing Playwright test harness instead of bypassing it with a standalone script. 3. Prefer a one-off Playwright spec inside the repo's existing Playwright runner over a standalone script. Only use a standalone script when there is no viable in-repo Playwright setup to reuse. 4. Reusing the runner means reusing the repo's real config, global setup, fixtures, env loading, and authentication/storage-state flow unless the user explicitly asks for something different. 5. Show only the relevant behavior. Skip unrelated setup whenever you can safely redirect, seed, deep-link, or reuse saved auth state. 6. Start the recording on the closest stable route or screen to the behavior being reviewed. If a stable deep link exists, use it. 7. Do not include upstream navigation through unrelat