bmad-testarch-ci

Scaffold CI/CD pipelines with test sharding, burn-in loops, and artifact collection.

Updated Mar 1, 2026
One-click install
npx skills add https://github.com/Hexalith/Hexalith.Parties --skill bmad-testarch-ci-hexalith
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-testarch-ci
Source: https://github.com/Hexalith/Hexalith.Parties/tree/main/.agents/skills/bmad-testarch-ci
Command: npx skills add https://github.com/Hexalith/Hexalith.Parties --skill bmad-testarch-ci-hexalith

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up a production-grade CI/CD pipeline for automated testing is repetitive and error-prone, requiring correct sharding, caching, flaky-test detection, and platform-specific YAML syntax across GitHub Actions, GitLab CI, Azure DevOps, Jenkins, Harness, and Circle CI. ## Core Features & Use Cases - Multi-Platform Pipeline Generation: Produces ready-to-commit CI configuration for GitHub Actions, GitLab CI, Azure DevOps, Jenkins, Harness, or Circle CI from built-in templates. - Test Optimization Patterns: Configures parallel sharding (4 shards by default), dependency and browser caching, failure-only artifact uploads, and a 10-iteration burn-in loop for flaky test detection. - Stack-Aware Adaptation: Auto-detects frontend, backend, fullstack, or mobile stacks and frameworks (Playwright, Cypress, Jest, Vitest, pytest, and more) and adjusts commands, browser installs, and stages accordingly. - Use Case: A team with a Playwright E2E suite asks the agent to set up CI; the skill detects the stack, writes .github/workflows/test.yml with lint, sharded test, burn-in, and report stages, plus helper scripts and documentation. ## Quick Start Ask the agent 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 pipeline with lint, sharded test execution, browser caching, and a burn-in stage. It writes the config to the correct path for your CI platform, such as .github/workflows/test.yml for GitHub Actions.

What CI platforms does this pipeline generator support?▼

It supports GitHub Actions, GitLab CI, Azure DevOps, Jenkins, Harness, and Circle CI. Templates are included for most platforms, and the platform is auto-detected from existing config files or the git remote.

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 on the first failure, surfacing non-deterministic tests. It runs on pull requests or a weekly schedule and uploads failure artifacts for debugging.

Does the pipeline work for backend-only projects without browsers?▼

Yes. When the stack is detected as backend-only, browser install steps are omitted and the burn-in stage is skipped by default, since burn-in targets UI flakiness. Test commands adapt to frameworks like pytest, Jest, Vitest, Go, or .NET.

How does the skill prevent script injection in GitHub Actions?▼

It never interpolates ${{ inputs.* }} or ${{ github.event.* }} directly in run blocks. User-controlled values are passed through env intermediaries and referenced as quoted shell variables, and the validation step scans generated YAML for unsafe patterns.