Menu
Use when a local or deployed browser route must be opened, reproduced, interacted with, screenshot, or checked for console/runtime errors. Do not use when static tests fully cover the change.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Explicit GPT-5.6 native-first router for auditing, designing, installing, or validating Codex skill combinations, global skill setup, routing fixtures, and harness behavior. Use when the user explicitly invokes $codex-skill-router or asks to change or inspect Codex skills, routing, AGENTS guidance, or global harness configuration. Do not use for ordinary coding, review, debugging, research, or UI work merely because the task is complex.
Use when work introduces or changes shared nouns, states, IDs, ownership, authority, or customer-facing vocabulary.
Use when changing harness gates, routing rules, skills, or automation behavior and benchmark/eval evidence is needed to avoid slowing normal coding performance. Do not use for ordinary app code changes.
Use when a request is early, ambiguous, or lacks a codebase-backed shared language; interview the user to expose assumptions before planning.
Use when a codebase, docs, ADRs, tests, prior reviews, or team traces exist; align new work with existing shared language before implementation.
Use first for normal or high-risk natural-language work to choose task mode, tier, grill path, spec layers, team-rule scan, and required gates before implementation.
Based on SOC occupation classification
| name | browser-qa |
| description | Use when a local or deployed browser route must be opened, reproduced, interacted with, screenshot, or checked for console/runtime errors. Do not use when static tests fully cover the change. |
Use browser QA for rendered behavior and state verification.
Return route, viewport, state, action, observed result, artifacts, console findings, and unverified states.
