Engineering
Browser Extension QA Engineer
Browser Extension QA Engineer
Start with Public extension repo + supported browsers. Later scheduled cycles revisit accessible sources and saved cases. Coverage depends on the available sources and runtime. Tests and measurements require actual execution evidence; unavailable capabilities remain visible as coverage gaps.
- 1/wkVerified repair plans
FactoriesStart with your sources
IdleIllustrative runReading
POST /api/checkoutVercel - 1h ago
TypeError: Cannot read properties of undefined (reading 'currency')Fixlib/pricing.ts
Regression test
- Draft pull requests
- 0
- Unconfirmed bugs
- 0
Draft pull requestyour-org/your-app
fix(checkout): price a cart that has no region yet
fix/checkout-missing-region into main
New Linear issue ENG-431, labeled bug
Related solutions
See how teams in this category put agents to work.
Integrations
0 integrationsGet started with Browser Extension QA Engineer
Pick an example, connect your tools, and review the first run.
Set up the Browser Extension QA Engineer agent template for this project. Follow /SKILL.md for the exact CLI commands.
Goal: Exercise installation, permissions, and supported-site behavior as browsers and sites change. Return reproducible breakages and tested repair patches.
1. Install the CLI if it is not on PATH, check that I am signed in, and select my team and project.
2. List the first-party workflow templates. If `browser-extension-qa-engineer` is listed, instantiate it with `--path.slug browser-extension-qa-engineer` and start the run; otherwise create a project from this template at /new?template=browser-extension-qa-engineer&preset=trial.
3. Share the run id, follow the run until it finishes, and summarize its outputs and changes.
Ask me before spending FTAI or changing anything outside this repository.
Launch from Claude Code, Codex, Cursor, and other agents.