Qa Verification

Fallback:

• If DevTools MCP is unavailable, capture Playwright trace/screenshots and browser console logs from the test run, and note the limitation.

Automated confirmation gate:

• Any UI change must complete the Web UI Verification steps before moving on.
• Do not wait for user approval; verification is automated evidence.

CLI Verification

Required evidence:

1. Command transcripts: command + stdout + stderr + exit code.
2. Non-interactive behavior: flags like --no-input, stdin via pipe, and - for stdin/stdout when supported.
3. Output formats: --json and plain output validated; schema stable if applicable.
4. Config precedence and location checks (flags/env/project/user/system; XDG if used).
5. CI command(s) run with green results.

Workflow:

1. Identify primary commands and flags touched by the change.
2. Run happy-path and failure-path commands; capture exit codes and streams.
3. Validate non-interactive paths (piped stdin, - for stdin/stdout).
4. Verify output formats and schema stability.
5. Verify config precedence and storage locations.
6. Record QA evidence in the task before closing.

Guardrails

• If repo QA instructions conflict with this skill, follow repo rules.
• If the work spans both UI and CLI, apply both checklists.