app-qalisted

Visually verify treq UI/behavior changes by driving the real app (real jj repo via NAPI, real Rust dispatch, jsdom-rendered React) with @testing-library/user-event and capturing before/after screenshots through the Chromium rasterization harness in scripts/screenshot/. Use explicitly when the user runs /app-qa or asks to screenshot, QA, or visually check a behavior. ALSO use proactively, without being asked, right after implementing or modifying anything that changes rendered UI or user-facing interaction: components under src/components/**, hooks under src/hooks/**, src/lib/** helpers that affect rendering, or Tauri commands under src-tauri/src/commands/** and src-tauri/src/core/** that back a UI flow. Do this before telling the user the change is done. A PostToolUse hook (.claude/hooks/post-edit-app-qa.sh) injects a reminder for exactly this case — treat that reminder as the trigger to run this skill, not just a suggestion.
treq-dev/treq · ★ 5 · Testing & QA · score 70

Install: claude install-skill treq-dev/treq

# App QA (screenshot-verified behavior checks) ## When to use - User invokes `/app-qa`, optionally naming a flow or component ("app-qa the workspace picker", "app-qa the merge conflict banner"). - Proactively, immediately after an Edit/Write/MultiEdit that changes UI-affecting code — don't wait to be asked. If you see `additionalContext` from `post-edit-app-qa.sh` naming a changed file, that *is* the request. ## Delegate grunt work and discovery to cheaper subagents Most of the cost of an app-qa run is search and mechanical legwork, not judgement. Push that to subagents on a cheaper model (`Agent` with `model: "haiku"`, or `"sonnet"` when the answer needs some reasoning) and keep the expensive context for the parts that actually need it. Run independent delegations in parallel in a single message. Good candidates — hand these off: - **Finding prior art.** Which `test/integration/**` or `test/*.test.tsx` scenario already builds the repo/workspace state this spec needs; whether a spec under `scripts/screenshot/specs/` already covers this flow; which spec is the closest shape to copy. Use `Explore` — it's read-only and returns the conclusion instead of dumping files. - **Locating selectors and wiring.** The `data-testid`, accessible role, or button label to drive; which component renders a given piece of copy; which UI flow a changed `src-tauri/` or `src/lib/` file actually backs. - **Tracing dispatch gaps.** When a flow hits a `not_implemented` stub, hav