Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

browser-qa

Sterne43

Forks7

Aktualisiert1. April 2026 um 00:59

Use when acting as `browser_debugger` to gather browser evidence, run the governed QA passes, and report PASS/FAIL/BLOCKED outcomes for UI-facing work. Do not use for application-code edits.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

thegeronimo

thegeronimo/hyperopen

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

Softwarequalitätssicherungsanalysten und -testerInformatik- und Mathematikberufe·SOC 15-1253

SKILL.md

readonly

name	browser-qa
description	Use when acting as `browser_debugger` to gather browser evidence, run the governed QA passes, and report PASS/FAIL/BLOCKED outcomes for UI-facing work. Do not use for application-code edits.

Browser QA

Use this skill when acting as the browser_debugger role for a multi-agent ticket.

Read First

/hyperopen/AGENTS.md
/hyperopen/docs/MULTI_AGENT.md
/hyperopen/docs/agent-guides/browser-qa.md
/hyperopen/docs/FRONTEND.md
/hyperopen/docs/runbooks/browser-live-inspection.md

Job

Reproduce the ticket in the browser when browser QA is required by the spec.
Use the existing browser-inspection MCP server and artifacts.
Report PASS, FAIL, or BLOCKED for all required passes, or emit an explicit skip when browser QA is not required.
End browser work by stopping active sessions. Use npm run browser:cleanup unless a narrower single-session stop is more appropriate.

Guardrails

Do not edit application code.
Use /hyperopen/tmp/browser-inspection/** for transient evidence.
Write /hyperopen/docs/qa/** only when the workflow calls for a durable UI note.

Expected Outputs

browser-report.json
Optional QA note under /hyperopen/docs/qa/

Mehr aus diesem Repository

gleiches Repository

acceptance-tests

thegeronimo/hyperopen

Use when acting as `acceptance_test_writer` to propose happy-path acceptance and integration coverage from an approved spec or ExecPlan. Do not use to materialize tests directly or to edit production code.

2026-05-1243

bug-flow

thegeronimo/hyperopen

Invoke explicitly with `$bug-flow` for unclear bugs, regressions, or failure investigations that need structured diagnosis, regression tests, the smallest fix, and findings-first review. Do not use for obvious one-line fixes or planned feature work.

2026-05-1243

edge-case-tests

thegeronimo/hyperopen

Use when acting as `edge_case_test_writer` to propose adversarial, boundary, and invariant coverage that complements acceptance coverage. Do not use to materialize tests or edit production code.

2026-05-1243

feature-flow

thegeronimo/hyperopen

Invoke explicitly with `$feature-flow` for complex features, significant refactors, or multi-file behavior changes that need an ExecPlan, proposed test coverage, RED-phase failing tests, implementation, and review. Do not use for tiny fixes, doc-only work, or purely local cleanup.

2026-05-1243

spec-writer

thegeronimo/hyperopen

Use when acting as `spec_writer` to create or refresh the active ExecPlan, clarify scope, and record acceptance criteria for a multi-agent ticket. Do not use for production-code edits or standalone prose cleanup.

2026-05-1243

browser-mcp-explore

thegeronimo/hyperopen

Use Browser MCP for exploratory browser debugging, live-session inspection, parity compare, design review, and selector or flow discovery before converting stable paths into Playwright.

2026-04-0143

name	browser-qa
description	Use when acting as `browser_debugger` to gather browser evidence, run the governed QA passes, and report PASS/FAIL/BLOCKED outcomes for UI-facing work. Do not use for application-code edits.

Browser QA

Use this skill when acting as the browser_debugger role for a multi-agent ticket.

Read First

/hyperopen/AGENTS.md
/hyperopen/docs/MULTI_AGENT.md
/hyperopen/docs/agent-guides/browser-qa.md
/hyperopen/docs/FRONTEND.md
/hyperopen/docs/runbooks/browser-live-inspection.md

Job

Reproduce the ticket in the browser when browser QA is required by the spec.
Use the existing browser-inspection MCP server and artifacts.
Report PASS, FAIL, or BLOCKED for all required passes, or emit an explicit skip when browser QA is not required.
End browser work by stopping active sessions. Use npm run browser:cleanup unless a narrower single-session stop is more appropriate.

Guardrails

Do not edit application code.
Use /hyperopen/tmp/browser-inspection/** for transient evidence.
Write /hyperopen/docs/qa/** only when the workflow calls for a durable UI note.

Expected Outputs

browser-report.json
Optional QA note under /hyperopen/docs/qa/