browse-qa
Skill15 starsChanged 8 months agoApache-2.0View on GitHub
QA a web or app feature from a ticket, URL, acceptance criteria, or plain-language description, then generate reusable browse flows for regression coverage. Uses the `browse` skill for the actual browser or simulator interaction and keeps the QA loop focused on scenarios, evidence, and report quality.
In this repository63 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- agent-browserSkill
- ast-grepSkill
- branch-review-before-prSkill
- browser-useSkill
- browseSkill
- bugfixSkill
- build-dmgSkill
- claude-reviewSkill
- codemapSkill
- code-simplifySkill
- codex-reviewSkill
- commitSkill
- cost-estimateSkill
- create-prSkill
- find-agentsSkill
- find-bugsSkill
- frontend-design-ui-uxSkill
- git-merge-expertSkill
- git-merge-expert-worktreeSkill
- kiro-reviewSkill
- laravel-filamentSkill
- laravelSkill
- lokeiSkill
- map-project-monorepoSkill
- map-projectSkill
- nextjsSkill
- plan-founder-reviewSkill
- plan-to-task-list-with-dagSkill
- pr-retroSkill
- run-parallel-agents-feature-buildSkill
- run-parallel-agents-feature-debugSkill
- rustSkill
- secretsSkill
- startSkill
- update-agent-learningsSkill
- update-claude-learningsSkill
- update-claude-settingsSkill
- update-skill-learningsSkill
- ast-grepSkill
- branch-review-before-prSkill
- codemapSkill
- code-simplifySkill
- commitSkill
- cost-estimateSkill
- create-prSkill
- find-bugsSkill
- frontend-design-ui-uxSkill
- git-merge-expertSkill
- git-merge-expert-worktreeSkill
- map-project-monorepoSkill
- map-projectSkill
- plan-founder-reviewSkill
- plan-to-task-list-with-dagSkill
- pr-retroSkill
- run-parallel-agents-feature-buildSkill
- run-parallel-agents-feature-debugSkill
- startSkill
- update-agent-learningsSkill
- The first 60 shown.
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. About 0 are common, 7 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 32
Use the browse skill for actual browser or simulator interaction.
- Distinctive: line 62
If the target or platform is ambiguous, ask before testing.
- Distinctive: line 75
Keep the plan small enough to execute in one session unless the user asked for a broad QA sweep.
- Very specific: line 81
Use Skill to invoke browse for:
- Very specific: line 91
keep the same browse session for one logical user journey unless isolation is intentional
- Distinctive: line 92
use headed or handoff mode only for real blockers like CAPTCHA, MFA, or OAuth walls
- Distinctive: line 99
When the scenario is stable and worth rerunning:
- Distinctive: line 105
Do not save noisy or half-manual recordings as regression artifacts.
- Very specific: line 128
Do not duplicate the full browse command manual inline.
- Distinctive: line 129
Do not guess a platform when the request is ambiguous.
- Distinctive: line 130
Do not save low-signal flows just to say a regression asset was created.
- Very specific: line 131
Do not add disable-model-invocation.
- Very specific: line 132
Do not add context: fork; results are usually needed in the current execution flow.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
<EXTREMELY-IMPORTANT>
This skill owns the QA plan and report, not the low-level browser command encyclopedia.Non-negotiable rules:
- Turn the incoming spec into explicit scenarios before testing.
- Confirm ambiguous targets or platforms before execution.
- Use the
browseskill for actual browser or simulator interaction. - Capture evidence for each failed or important scenario.
- Save rerunnable flows only when they are cleanly scoped and valuable for regression.
</EXTREMELY-IMPORTANT>
browse-qa
Inputs
$request: Ticket, URL, app target, acceptance criteria, or plain-language QA request
Goal
Produce a credible QA run that:
- turns a vague request into explicit scenarios
- runs those scenarios against the real target
- captures evidence for passes and failures
- saves rerunnable browse flows when appropriate
- returns a clean QA report the user can act on
Step 0: Resolve the target and spec
Work out:
- what feature is being tested
- the platform: web, iOS simulator, Android emulator, or macOS app
- the target URL, build artifact, or app identifier
- the acceptance criteria or expected outcomes
If the target or platform is ambiguous, ask before testing.
Success criteria: The QA target and acceptance criteria are explicit.
Step 1: Build the scenario list
Break the request into:
- happy path
- validation or error path
- edge cases
- exploratory probes worth trying after the stated acceptance criteria
Keep the plan small enough to execute in one session unless the user asked for a broad QA sweep.
Success criteria: There is a concrete scenario list with expected outcomes.
Step 2: Execute with the browse skill
Use Skill to invoke browse for:
- navigation
- page stabilization
- interactive element discovery
- clicks, fills, and submissions
- screenshots, console logs, and network inspection
Rules:
- keep the same browse session for one logical user journey unless isolation is intentional
- use headed or handoff mode only for real blockers like CAPTCHA, MFA, or OAuth walls
- save screenshots and flow artifacts under the browse session directories
Success criteria: Each scenario is executed against the real target with enough evidence to judge pass or fail.
Step 3: Record reusable regression flows
When the scenario is stable and worth rerunning:
- record the flow
- split unrelated user journeys into separate flow files
- give each saved flow a descriptive name
Do not save noisy or half-manual recordings as regression artifacts.
Success criteria: Saved flows are independently rerunnable and map to clear scenarios.
Step 4: Report results
For each scenario, record:
- expected result
- actual result
- pass or fail
- evidence such as screenshot path, console error, or network symptom
Also report:
- exploratory findings
- regression flow files created
- blockers that prevented full verification
Success criteria: Another engineer can understand the QA outcome without replaying the whole session first.
Guardrails
- Do not duplicate the full browse command manual inline; use the
browseskill. - Do not guess a platform when the request is ambiguous.
- Do not save low-signal flows just to say a regression asset was created.
- Do not add
disable-model-invocation; QA should stay available when the user asks for it. - Do not add
context: fork; results are usually needed in the current execution flow.
Output Contract
Report:
- target tested
- scenarios executed
- pass/fail result for each scenario
- evidence captured
- regression flow files created
- blockers or uncovered gaps
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

