Cross Browser QA
SkillWeb & browsingRun cross-browser QA for websites and apps. Use before production or after CSS, media, forms, animation, canvas, layout, or interaction changes to test Chromium, WebKit/Safari-like, and Firefox behavior, browser-specific CSS/media issues, focus/keyboard differences, and responsive rendering.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Cross Browser QA skill
What this skill tells your AI
The instructions your AI receives, as published by thegoat395/codex-skills in skills/cross-browser-qa/SKILL.md and read by ahel’s review.
Use this skill to catch browser-specific issues that one local Chromium pass will miss.
Workflow
- Inspect the affected surface, relevant project scripts, target URL and available inspection tooling; reuse existing context.
- Read Cross Browser QA Guide before claiming the site is ready.
- Compare the affected path across the supported available engines, concentrating on changed CSS, focus, scrolling, media and input behavior. Record engine/version and unavailable coverage.
- Fix issues when they are in scope; otherwise record exact evidence and remaining risk.
- Summarize commands, URLs, screenshots/checks, changed files, and what was not tested.
Scoped execution
Apply the shared web contract once when execution crosses phases; reuse it if already read. Load only the specialist guidance relevant to the requested surface and deliverable.
Scope and evidence
Record browser engine, version, OS, viewport and tested core path. Playwright WebKit is WebKit evidence, not actual Safari or real-device certification. Mark unavailable browsers untested.
Signals
- GitHub stars
- 124
- Forks
- 48
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
cross-browser-qa- Source
- github.com/thegoat395/codex-skills