← ClaudeAtlas

ci-setuplisted

Creates or repairs GitHub Actions workflows that run the generated Playwright suites, publish reports, and push results back to TestRail. Use this skill when a test repository has no CI, when the user asks to run tests on every pull request or nightly, when CI is failing for environment or secret reasons, or as the step after the first test PR is merged. Also use it to split a slow suite into a fast smoke gate and a full nightly run.
YevheniiaQA/qa-agent-toolkit · ★ 0 · AI & Automation · score 72
Install: claude install-skill YevheniiaQA/qa-agent-toolkit
# CI Setup (GitHub Actions) Tests that only run on someone's laptop stop running. CI is what turns a generated suite into a standing safety net. ## Disabled integrations Follow `qa-conventions` → *Disabled integrations* for the CI host (`github`) and the TMS it reports to: 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:** write the workflow files into the repository and validate them locally (`actionlint` where available). Do not push, create secrets or call the API. A results-publishing step for a TMS that is disabled stays out of the workflow. ## The two-tier pattern One workflow is the wrong shape. Split by purpose: | Workflow | Trigger | Scope | Target duration | |---|---|---|---| | Smoke gate | Pull request, push to main | `@smoke` tag only | under 5 minutes | | Full regression | Nightly schedule, manual dispatch | Everything | however long it takes | A suite that adds ten minutes to every pull request gets disabled within a month. A five-minute gate plus a nightly full run keeps both the feedback loop and the coverage. ## Smoke gate workflow ```yaml name: QA smoke on: pull_request: push: { branches: [main] } jobs: smoke: runs-on: ubuntu-latest timeout-minutes: 15 steps: - uses: actions/checkout@v4 - uses: actions/setup-node@v4 with: { node-version: 20, cache: npm } - run: npm ci - run: npx pl