blueif16/amazing-claude-code-plugins/browser-test
Claude Code and agent skill by blueif16/amazing-claude-code-plugins
- community
Checking that the SKILL.md file is still in the repository.
Generate Playwright test scripts for browser-based acceptance verification. Load when DAG tasks touch UI, routes, or user-facing API responses.
Install
npx vskill@latest install blueif16/amazing-claude-code-plugins/browser-testSKILL.md
Browser Test — From Acceptance Criteria to Playwright Scripts
When This Skill Activates
A task needs browser_acceptance when its scope touches:
- UI components, pages, layouts, forms
- Routes or navigation (frontend or API endpoints returning HTML)
- User-visible behavior (toasts, modals, redirects, error states)
- API responses that the frontend consumes (verify the contract end-to-end)
Tasks that are pure backend (DB migrations, config, internal services) do NOT need browser testing.
browser_acceptance Format
Add to any DAG task alongside the CLI acceptance field:
Rules
- Steps are natural language, not selectors. Generated Playwright uses
getByRole,getByText, accessibility tree. Never hardcode CSS selectors — this makes tests resilient to UI changes. - Keep tests minimal. 1-3 tests per task, 2-5 steps each. Test the acceptance criteria, not the entire app.
- Always include console/network assertions. Even if the UI looks right, runtime errors indicate broken code.
- Inherit project defaults from `.godag/quality.md` if it exists. Only specify per-task overrides.
Quality Bar File (Optional)
If .godag/quality.md exists in the project root, read it during DAG generation for project-wide defaults:
When generating browser_acceptance, inherit these defaults. Only add task-specific assertions for behavior unique to that task.
Playwright Script Generation
The orchestrator generates .godag/tests/{task_id}.spec.ts before running. Template:
Playwright Config
Generate .godag/tests/playwright.config.ts once per run if absent:
Screenshots on failure land in test-results/ automatically. JSON reporter writes to .godag/context/. Traces retained for deep debugging.
Running
Exit code 0 = pass, non-zero = fail. Orchestrator checks exit code only, then spawns summarizer.
Summarizer Subagent
After Playwright runs, orchestrator spawns a disposable Task-tool subagent to distill results. This keeps verbose JSON + screenshots out of the orchestrator's context.
Spawn Prompt
What the Orchestrator Sees
Only the godag-result: ~30 tokens. The verdict.md stays on disk for the retry agent.
Retry Flow
When browser verification fails, the retry implementation subagent gets:
Retry agent reads verdict in its own fresh context. Never sees raw JSON or orchestrator reasoning.
Dev Server Management
Before first browser test:
After all tasks complete:
Prerequisites Check
Before generating any test:
If absent: "Browser testing 需要 Playwright。安装: npm init playwright@latest"
Skip browser_acceptance gracefully if unavailable — fall back to CLI-only acceptance.
Security
- Security scanPassed, 90 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingGoDag/skills/browser-test/SKILL.md
Popularity
- 7-day trend score
- 0
Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/blueif16/amazing-claude-code-plugins/browser-test)