bmad-testarch-ci

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

1|Updated Sep 18, 2026
One-click install
npx skills add https://github.com/PastaSus/egg-defender --skill bmad-testarch-ci-pastasus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-testarch-ci
Source: https://github.com/PastaSus/egg-defender/tree/main/.agents/skills/bmad-testarch-ci
Command: npx skills add https://github.com/PastaSus/egg-defender --skill bmad-testarch-ci-pastasus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up a CI/CD pipeline for automated testing requires platform-specific YAML syntax, sharding strategies, flaky-test detection, and security hardening that teams often get wrong or skip entirely. ## 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 Test Execution: Auto-detects frontend, backend, fullstack, or mobile stacks and configures the right test commands, browser installs, caching, and parallel sharding. - Quality Gates & Security: Adds burn-in loops for flaky test detection, pass-rate thresholds, optional Pact contract-testing stages, and enforces script-injection-safe patterns for reusable workflows. - Use Case: A team with a Playwright E2E suite asks to set up CI; the skill detects the stack, generates a GitHub Actions workflow with 4-way sharding and a weekly burn-in cron, scaffolds helper scripts, and writes docs/ci.md with a secrets checklist. ## Quick Start Ask the assistant to set up a CI pipeline with quality gates for this repository and let it detect the 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 this skill and it detects your Playwright config, then generates a platform-specific pipeline with lint, sharded test execution, browser caching, and a burn-in stage. It also scaffolds helper scripts like ci-local.sh and documentation for required secrets.

Which CI platforms does this pipeline generator support?

It supports GitHub Actions, GitLab CI, Azure DevOps, Harness, Jenkins, and Circle CI. Templates are included for GitHub Actions, GitLab CI, Azure DevOps, and Harness; Jenkins and Circle CI configs are generated from first principles.

What is a burn-in loop in CI testing?

A burn-in loop runs the test suite repeatedly (typically 10 iterations) to detect flaky tests before they reach main. It runs on pull requests or a scheduled cron and fails the pipeline if any iteration fails, uploading artifacts for debugging.

Does the pipeline work for backend-only projects?

Yes. When the detected stack is backend-only, the pipeline skips Playwright browser installs and omits the burn-in stage by default, since burn-in targets UI flakiness. Backend frameworks like pytest, Jest, Vitest, Go, Maven, and .NET are supported.

How does the skill prevent script injection in GitHub Actions?

It never interpolates ${{ inputs.* }} or ${{ github.event.* }} directly in run blocks. Instead it passes them through env: intermediaries referenced as quoted variables, and the validation step scans generated YAML for unsafe patterns.

When should I not use this CI scaffolding workflow?

Do not run it before a test framework is configured and passing locally; the preflight step halts in that case and directs you to set up the framework first. It is also a one-time setup per repo, not a per-change tool.