跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
浏览器与自动化

cross-browser-qa

Run 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.

TheGoat395 · 已有 AI 审核记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add TheGoat395/Codex-Skills --skill cross-browser-qa

技能说明


name: cross-browser-qa description: "Run 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."

Cross Browser QA

Use this skill to catch browser-specific issues that one local Chromium pass will miss.

Workflow

  1. Inspect the project, scripts, routes, local/deployed URL, production surfaces, and available QA/deployment tooling.
  2. Read Cross Browser QA Guide before claiming the site is ready.
  3. Run the narrowest meaningful checks for the risk: visual, mobile, accessibility, performance, forms, media, SEO, analytics, deployment, or handoff.
  4. Fix issues when they are in scope; otherwise record exact evidence and remaining risk.
  5. Summarize commands, URLs, screenshots/checks, changed files, and what was not tested.

Always Protect

  • Inspect before changing or shipping: framework, package scripts, build output, routes, forms, media, animation stack, deployment target, environment variables, analytics, SEO metadata, accessibility risks, and available browser QA tooling.
  • Do not claim something was tested unless it was actually tested; report exact commands, URLs, screenshots, viewports, failures, skipped checks, and remaining risk.
  • Verify desktop and mobile rendered output, not only source code. For visual or motion work, inspect screenshots, browser behavior, console errors, network failures, and responsive layout.
  • Treat forms, checkout, booking, CMS content, analytics, environment variables, and deployments as production surfaces with error, loading, empty, success, and rollback states.
  • Respect accessibility, performance, reduced-motion, and no-JavaScript/no-WebGL/no-autoplay fallbacks where relevant.
  • Keep secrets out of code, logs, screenshots, summaries, widgets, and committed files.
  • Prefer project-local tooling and existing scripts before adding dependencies. Explain any new dependency before installing it.
  • End with a concise handoff: changed files, commands run, checks passed, checks not run, deployment URL if any, and next risks.