bmad-testarch-ci

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

Updated Sep 3, 2026
One-click install
npx skills add https://github.com/watchthelight/shatterfish --skill bmad-testarch-ci-watchthelight
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-testarch-ci
Source: https://github.com/watchthelight/shatterfish/tree/main/.claude/skills/bmad-testarch-ci
Command: npx skills add https://github.com/watchthelight/shatterfish --skill bmad-testarch-ci-watchthelight

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up a production-grade CI/CD pipeline for automated testing requires platform-specific YAML, correct sharding, caching, flaky-test detection, and security hardening, which is error-prone to write by hand. This Skill scaffolds the entire pipeline from detected project context. ## Core Features & Use Cases - Multi-Platform Pipeline Generation: Produces ready-to-commit configurations for GitHub Actions, GitLab CI, Azure DevOps, Harness, Jenkins, and Circle CI from templates. - Test Optimization Built In: Configures parallel sharding (4 shards by default), dependency and browser caching, burn-in loops for flaky test detection, and failure-only artifact uploads. - Security Hardening: Enforces script-injection prevention by routing user-controlled GitHub contexts through env intermediaries, and validates generated YAML against a checklist. - Use Case: A team with a Playwright E2E suite asks to set up CI; the Skill detects the stack, generates .github/workflows/test.yml with lint, sharded test, burn-in, and report stages, plus helper scripts and docs. ## Quick Start Ask the agent to set up a CI pipeline with quality gates for this repository's test suite.

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 loop. It supports GitHub Actions, GitLab CI, Azure DevOps, Harness, Jenkins, and Circle CI.

How to detect flaky tests in CI with a burn-in loop?

The generated pipeline includes a burn-in stage that runs the test suite 10 times and fails on any failure, surfacing flaky tests. It triggers on pull requests or a weekly schedule and uploads artifacts only on failure.

Which 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, and can be overridden in the workflow configuration.

Does the generated GitHub Actions workflow prevent script injection?

Yes. User-controlled contexts like inputs and github.event values are never interpolated directly into run blocks; they are passed through env intermediaries and referenced as quoted variables. The validation step scans generated YAML for unsafe patterns.

Can I use this for a backend-only project without browser tests?

Yes. When the detected stack is 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 the detected language and framework.