qa-setup
/qa-setup
WAY 0 — prepare the current project for DevOps QA Agent — test runner in qa-artifacts/, issue tracker and code host (GitLab, GitHub, Jira, Azure DevOps, Bitbucket), per-project .env values, access check. Use when the user says "qa setup", "set up qa", "init qa agent", or when another WAY finds qa-artifacts/ or its settings missing.
- Author
- ghassenazzouz ↗
- Repository
- claude-qa-agent ↗
- Licence
- MIT
- Last repository change
- 18.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 18.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
WAY 0 — prepare the current project for DevOps QA Agent — test runner in qa-artifacts/, issue tracker and code host (GitLab, GitHub, Jira, Azure DevOps, Bitbucket), per-project .env values, access check. Use when the user says "qa setup", "set up qa", "init qa agent", or when another WAY finds qa-artifacts/ or its settings missing.
Triggers from the description
Original author description
WAY 0 — prepare the current project for DevOps QA Agent — test runner in qa-artifacts/, issue tracker and code host (GitLab, GitHub, Jira, Azure DevOps, Bitbucket), per-project .env values, access check. Use when the user says "qa setup", "set up qa", "init qa agent", or when another WAY finds qa-artifacts/ or its settings missing.
How it works
- 1. Test runner → qa-artifacts/
- 2. Providers
- 3. Project values → .env (project root)
- 4. Tools and access
- 5. Summary
SKILL.md preview
---
name: qa-setup
description: WAY 0 — prepare the current project for DevOps QA Agent — test runner in qa-artifacts/, issue tracker and code host (GitLab, GitHub, Jira, Azure DevOps, Bitbucket), per-project .env values, access check. Use when the user says "qa setup", "set up qa", "init qa agent", or when another WAY finds qa-artifacts/ or its settings missing.
---
# WAY 0 — QA Setup
Run once per project. Ask before changing anything that already exists.
## 1. Test runner → `qa-artifacts/`
- If `qa-artifacts/playwright.config.ts` is missing, copy `${CLAUDE_PLUGIN_ROOT}/runner-template/` (`package.json`, `playwright.config.ts`, `README.md`) into it
- If a config already exists, compare it with the **Playwright config contract** in `test-execution-agent` and list the differences. Don't overwrite it
- From `qa-artifacts/`: `npm install`, then `npx playwright install chromium`. Report `npx playwright --version`
- For WAY 18 (exploratory) only, install the Playwright MCP's own browser: `npx -y @playwright/mcp@0.0.83 install-browser chrome-for-testing`
## 2. Providers
Ask, or detect from `git remote -v` and the connected MCP servers, then confirm:
- **Issue tracker** (`QA_TRACKER`): `gitlab` · `github` · `jira` · `azure-devops`
- **Code host / CI** (`QA_CODE_HOST`): `gitlab` · `github` · `azure-devops` · `bitbucket`
## 3. Project values → `.env` (project root)
Add only the keys for the chosen providers, keep existing values, and ask for each one (or leave it empty with a comment):
```
QA_TRACKER=github
QA_CODE_HOST=github
STAGING_URL=
PROD_URL=
FEATURE_BASE_URL= # preview apps: FEATURE_BASE_URL/<branch>
API_TEST_TOKEN= # test-account token for API tests, never a real user's
UI_TEST_USER= # optional test account for signed-in UI regressions and WAY 18 exploration
UI_TEST_PASSWORD=
API_TEST_TOKEN_B= # optional second test account (WAY 17 ownership workflows)
# <SERVICE>_BASE_URL= / <SERVICE>_TOKEN= # E2E API only, one pair per service (ORDERS_BASE_URL…)
API_PERF_THRESHOLD_MS=2000
# gitlab GITLAB_PROJECT_ID= (token: plugin settings, or .mcp.json from a clone)
# github GITHUB_REPO=owner/repo (auth: `gh auth login`)
# jira JIRA_BASE_URL= JIRA_PROJECT_KEY= JIRA_EMAIL= JIRA_API_TOKEN= (or a connected Atlassian MCP server)
# azure-devops AZDO_ORG_URL= AZDO_PROJECT= AZDO_REPO= AZURE_DEVOPS_EXT_PAT=
# bitbucket BITBUCKET_WORKSPACE= BITBUCKET_REPO= BITBUCKET_EMAIL= BITBUCKET_API_TOKEN=
```
Never echo secret values back. Make sure `.gitignore` covers `.env` and `qa-artifacts/` (add the missing lines with the user's OK).
## 4. Tools and access
For each chosen provider, check the tool its skill needs:
| Provider | Tool check |
|---|---|
| gitlab | `/mcp` shows the GitLab server connected (plugin: set the URL/token with `/plugin configure qa-agent@devops-qa-agent`; clone: `.mcp.json`) |
| github | `gh auth status` |
| jira | an Atlassian MCP server connected, **or** the REST settings above |
| azure-devops | `az version` plus the `azure-devops` extension (`az extension add --name azure-devops`) |
| bitbucket | `curl` plus the settings above |
Then run `project.check` (per `tracker` → the provider skill) for the tracker and the code host, and report the project or repo name each returns. On GitHub, offer two one-time setups (`provider-github`): the `tracker` label set, and the `qa-artifacts` prerelease that screenshots are attached to. With that release in place, later WAYs attach screenshots without asking.
## 5. Summary
Print what was created, changed, or skipped, plus a first command to try, e.g. `write it "<a small feature of this app>" App: <STAGING_URL>`.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · ghassenazzouz/claude-qa-agent | 100 | MIT |
| jirayusueb/qa-stack | 100 | Apache-2.0 |
Database snapshot: 13.11.2026 · package version dee188867bfa (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90check-devops
Audits the current project against a 312-item backend, database, security, DevOps and distributed-systems checklist and writes an evidence-backed status report. Use when the user says "check-devops", types /check-devops, or asks for a production-readiness / DevOps / backend audit of the project. - 100devops
Use when unsure whether a request is a GitHub or Azure DevOps operation, or when someone says "devops help", "connect to devops", "check my work items or PRs", "devops?". Routes to devops-github or devops-azure based on intent. Also use as a fallback when a request doesn't clearly map to either one. - 100ci-test-setup
WAY 10 — make the generated playwright-bdd suites run in CI on every MR/PR, on the default branch, and on schedules, without Claude — GitLab CI, GitHub Actions, Azure Pipelines, or Bitbucket Pipelines. Use when the user says "ci setup", "add tests to ci", "run tests in… - 90diagnose-ci
WAY 5 — diagnose a failed CI run (GitLab pipeline, GitHub Actions run, Azure Pipelines run, Bitbucket pipeline). Use when the user says "ci it", "diagnose ci", "fix ci", "why did ci fail", "check pipeline" with a run URL or ID. - 100init-env
Generate .env.example files, document all environment variables, set up .claude/settings.local.json permissions, and configure deployment secret management. Use when the user says "init env", "set up env", "create env example", "document env vars", "environment setup", "add env… - 100azure-devops
Set up Azure Pipelines for CI/CD, configure build and release pipelines, manage Azure DevOps projects, and integrate with Azure services. Use when working with Azure DevOps Services or Server for enterprise DevOps workflows.