bmad-testarch-ci

Generates CI/CD pipeline configurations with test sharding, burn-in loops, and quality gates.

2|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/Wizarck/nexandro --skill bmad-testarch-ci-wizarck
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-testarch-ci
Source: https://github.com/Wizarck/nexandro/tree/main/skills/bmad-testarch-ci
Command: npx skills add https://github.com/Wizarck/nexandro --skill bmad-testarch-ci-wizarck

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Setting up a CI/CD pipeline for automated test execution requires platform-specific YAML knowledge, correct sharding configuration, flaky-test detection, and security hardening against script injection. This Skill scaffolds a complete, validated pipeline configuration so teams do not have to write it from scratch. ## Core Features & Use Cases - Multi-Platform Pipeline Generation: Produces ready-to-adapt pipeline configs for GitHub Actions, GitLab CI, Azure DevOps, Harness, Jenkins, and Circle CI with lint, test, burn-in, and report stages. - Stack-Aware Adaptation: Auto-detects frontend, backend, or fullstack stacks and frameworks (Playwright, Cypress, Jest, Vitest, pytest, Go, .NET, Ruby) and adjusts browser installs, caching, and test commands accordingly. - Flaky Test Detection & Quality Gates: Configures parallel sharding (4 shards by default), 10-iteration burn-in loops, pass-rate thresholds, and optional Pact contract-testing gates. - Security Hardening: Enforces script-injection prevention by routing user-controlled inputs through env intermediaries and validating generated YAML against a checklist. - Use Case: A team with a Playwright test suite asks the agent to set up CI; the Skill detects the stack, generates a GitHub Actions workflow with sharding and burn-in, and validates it against a compliance checklist. ## Quick Start Ask the agent to set up a CI pipeline with quality gates for your repository and let it detect your platform and test framework automatically.

Frequently Asked Questions about bmad-testarch-ci

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up a CI pipeline for Playwright tests?▼

Run the workflow and it detects your Playwright config, then generates a pipeline with lint, sharded test execution, browser caching, and a burn-in stage. Templates exist for GitHub Actions, GitLab CI, Azure DevOps, and Harness.

What CI platforms does this pipeline generator support?▼

It supports GitHub Actions, GitLab CI, Azure DevOps, Harness, Jenkins, and Circle CI. The platform is auto-detected from existing config files or the git remote, with GitHub Actions as the default fallback.

How does burn-in testing detect flaky tests in CI?▼

The burn-in stage runs the test suite 10 times in a loop and fails the pipeline if any iteration fails, surfacing intermittent failures. It targets UI flakiness and is skipped by default for backend-only stacks.

Can I use this for backend-only projects without browser tests?▼

Yes. When the stack is detected as backend, the generated pipeline omits Playwright browser installs and the burn-in stage, and uses framework-appropriate commands such as pytest, go test, dotnet test, or rspec.

Why must GitHub Actions inputs go through env variables?▼

Interpolating ${{ inputs.* }} or github.event values directly in run blocks allows script injection from user-controlled content like PR titles. The Skill routes them through env intermediaries referenced as quoted shell variables to prevent this.

What are the prerequisites before running the CI setup workflow?▼

You need an initialized git repository, a configured test framework, and tests that pass locally. If no test framework is detected, the workflow halts and directs you to run the framework setup workflow first.