Engineering

Installation QA Engineer

Start with Public package or repo + environments. 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.

Start with Start with your sources Try the demo

1/wkVerified repair plans

FactoriesStart with your sources

IdleIllustrative run

Reading

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

Integrations

0 integrations

Get started with Installation QA Engineer

Pick an example, connect your tools, and review the first run.

Use template Try the demo

Set up the Installation QA Engineer agent template for this project. Follow /SKILL.md for the exact CLI commands. Goal: Recreate installation and first-run setup across supported environments, investigate failures, and deliver working recipes and repair patches for each release. 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 `installation-qa-engineer` is listed, instantiate it with `--path.slug installation-qa-engineer` and start the run; otherwise create a project from this template at /new?template=installation-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.

Related solutions

Integrations

Get started with Installation QA Engineer