initlisted

Set up the QA framework in a project. Works out the stack, writes qa.config.yml, and drops in a CI file. Use when starting on a repo that has no qa.config.yml, when qa-context says no config was found, or when the user says set this up, init, or wire this in.
eduramos21/qa-automation-framework · ★ 0 · Testing & QA · score 66

Install: claude install-skill eduramos21/qa-automation-framework

# Set up a project Input: `$ARGUMENTS`, optionally a path. Otherwise the current repo. The goal is one `qa.config.yml` that is true. A config that guesses wrong is worse than no config, because every agent afterwards trusts it. ## Steps **1. Look before asking.** Work out what you can from the repo: | Look at | Tells you | |---|---| | `package.json`, `requirements.txt`, `pom.xml`, `go.mod`, `*.csproj` | language | | dependencies and dev dependencies | runner. `@playwright/test`, `selenium`, `cypress`, `pytest`, `junit`, `appium` | | `playwright.config.*`, `pytest.ini`, `wdio.conf.*`, `cypress.config.*`, `testng.xml` | runner, and often where tests live | | existing test folders | `stacks.<platform>.root` and `layout` | | `.github/workflows/`, `.gitlab-ci.yml`, `Jenkinsfile`, `.circleci/` | `ci.provider` | | `.git/config` remote, existing issue links in commits | `tracker.provider` | | a `docs/`, `specs/` or `requirements/` folder | `requirements.source` and path | | how existing tests pick elements | `policies.test_id_attribute` | **2. Match a profile.** List what is in `profiles/` in the plugin, plus any `profiles/` next to the project. Three outcomes: - **Nothing matches the language and runner.** Say so and run `/qa:profile`, which reads their suite and drafts one. Do not force a near match, a Selenium project pointed at the Playwright profile generates code that does not compile. - **One matches and the repo has no tests yet.** Use it as is. - **One matches and