bmad-testarch-ci

Generate CI/CD pipeline scaffolds with test execution, parallel sharding, and artifact reporting.

Updated Feb 11, 2026
One-click install
npx skills add https://github.com/mschuerig/peach-ios --skill bmad-testarch-ci-mschuerig
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-testarch-ci
Source: https://github.com/mschuerig/peach-ios/tree/main/_bmad/tea/workflows/testarch/bmad-testarch-ci
Command: npx skills add https://github.com/mschuerig/peach-ios --skill bmad-testarch-ci-mschuerig

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams bootstrap a complete CI/CD pipeline tailored for test execution, sharding, burn-in loops, and artifact reporting, reducing setup time and consistency gaps across projects.

Core Features & Use Cases

  • Platform-specific templates for GitHub Actions, GitLab CI, Azure DevOps, CircleCI, Jenkins, and Harness
  • Parallel test sharding and burn-in loops to detect flaky tests
  • Artifact collection and test result visualization across environments
  • Clear validation and onboarding guidance to ensure reliable pipelines

Quick Start

Run the tool to generate a ready-to-use CI pipeline configured for your project's stack and framework.

Frequently Asked Questions about bmad-testarch-ci

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

FAQPage Schema
How do I scaffold a CI/CD pipeline with parallel test sharding and burn-in loops?

To scaffold a CI/CD pipeline with test sharding and burn-in loops, use a template-driven generator that produces platform-specific YAML or Groovy files. This ensures parallel execution and flaky test detection across your chosen environment.

What is test sharding and burn-in in CI/CD automation?

Test sharding splits test suites into parallel chunks for faster execution, while burn-in loops repeatedly run tests to detect flaky behavior. Both are automated within a generated CI/CD pipeline scaffold.

Does this CI pipeline generator work with GitHub Actions, GitLab CI, and Azure DevOps?

Yes, the CI pipeline generator works with GitHub Actions, GitLab CI, Azure DevOps, Jenkins, Harness, and CircleCI. It adapts to frontend, backend, or fullstack stacks using platform-specific templates.

How do I collect test artifacts and results across different CI platforms?

You collect test artifacts and results by generating a pipeline scaffold with built-in artifact collection and reporting steps. The templates include visualization and validation steps tailored to your specific platform.

Can I use one template to bootstrap test pipelines for both frontend and backend stacks?

Yes, you can bootstrap test pipelines for frontend, backend, or fullstack stacks using a single template-driven generator. It safely adapts platform-specific configurations to match your project's framework and stack.

Why do flaky tests keep passing locally but failing in my CI pipeline?

Flaky tests often pass locally but fail in CI due to race conditions or environment inconsistencies. Running burn-in loops within your generated CI pipeline repeatedly executes tests to surface and isolate these flaky failures.