pr-creatorlisted
Install: claude install-skill YevheniiaQA/qa-agent-toolkit
# MR Creator
Generated tests land in a repository that already has conventions, fixtures, and a
CI pipeline. Dropping files in and opening a PR that fails to compile wastes a
reviewer's afternoon and teaches the team to distrust the whole pipeline.
## Disabled integrations
Follow `qa-conventions` → *Disabled integrations* for the git host (`github`, `gitlab`, `bitbucket`): read `INTEGRATIONS`, skip a
system that is not listed, report it as `➖ <system> disabled for this project`, never route
around a `qa-guard` block.
**Local alternative:** run the compatibility analysis and validation as usual, commit on a local branch, and write the PR description to `PR_DESCRIPTION.md` in the test project. Never push. The engineer opens the PR, or enables the integration.
## Compatibility analysis first
Before copying a single file, compare the generated project against the target
repository and report conflicts:
| Check | What goes wrong |
|---|---|
| Fixture names | Generated `api` fixture collides with an existing one of different shape |
| Base classes / page objects | Target already has a `BasePage`; generated code has its own |
| Config | Target's `playwright.config.ts` defines projects, reporters, baseURL — generated config must merge, not replace |
| Dependencies | Version mismatch on `@playwright/test`, `zod`, `@axe-core/playwright` |
| Env vars | Names differ (`API_BASE_URL` vs `BASE_API_URL`) |
| tsconfig | Path aliases, `strict` mode, target ES version |
| Lint rules | Ta