gap-app-v2

Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", "test this app/site/platform", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.

Use for any Taskless task. Trigger when the user mentions Taskless by name, or when their request involves the .taskless/ directory or files in it (rules, rule-tests, rule-metadata). Specifically: - "create/add/write a taskless rule for X" - "improve/fix/iterate on this taskless rule" - "delete/remove this taskless rule" - "run taskless", "taskless check", "validate against taskless rules" - "taskless login/logout/status", "is taskless connected" - "add taskless to CI", "wire taskless into github actions" - "onboard with taskless", "set up taskless for this project" Also trigger on any request to add/write/create a lint or code rule, including ones that name a specific tool (eslint, ruff, biome, stylelint, ast-grep). Naming a tool ENGAGES this skill's routing flow via `taskless help route`; it does NOT suppress the skill.

Use for any Taskless task. Trigger when the user mentions Taskless by name, or when their request involves the .taskless/ directory or files in it (rules, rule-tests, rule-metadata). Specifically: - "create/add/write a taskless rule for X" - "improve/fix/iterate on this taskless rule" - "delete/remove this taskless rule" - "run taskless", "taskless check", "validate against taskless rules" - "taskless login/logout/status", "is taskless connected" - "add taskless to CI", "wire taskless into github actions" - "onboard with taskless", "set up taskless for this project" Also trigger on any request to add/write/create a lint or code rule, including ones that name a specific tool (eslint, ruff, biome, stylelint, ast-grep). Naming a tool ENGAGES this skill's routing flow via `taskless help route`; it does NOT suppress the skill.

Execute a QA test plan using agent-browser against localhost:3000. Uses Privy test accounts (fixed OTP) for authenticated scenarios. Always tests locally, never against preview URLs.

Analyze a PR diff and generate a strict, risk-prioritized QA test plan for frontend changes. Separates public scenarios from authenticated scenarios. Both run in CI using Privy test accounts for auth.