bmad-testarch-ci

Scaffolds CI/CD pipelines with parallel test sharding, burn-in loops, and quality gates.

6|Updated Aug 29, 2026
One-click install
npx skills add https://github.com/HordRicJr/Akomagni --skill bmad-testarch-ci-hordricjr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-testarch-ci
Source: https://github.com/HordRicJr/Akomagni/tree/main/bmad-core/.agents/skills/bmad-testarch-ci
Command: npx skills add https://github.com/HordRicJr/Akomagni --skill bmad-testarch-ci-hordricjr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up a production-grade CI/CD pipeline for test execution requires platform-specific YAML, sharding strategy, flaky-test detection, caching, and security hardening, which is error-prone to write by hand. This Skill generates a complete, validated pipeline configuration tailored to your stack and CI platform. ## Core Features & Use Cases - Multi-Platform Pipeline Generation: Produces ready-to-use configurations for GitHub Actions, GitLab CI, Azure DevOps, Harness, Jenkins, and Circle CI from built-in templates. - Test Optimization Built In: Configures 4-way parallel sharding, dependency and browser caching, failure-only artifact collection, and a 10-iteration burn-in loop for flaky test detection. - Security and Validation: Enforces script-injection prevention (env: intermediaries for user-controlled inputs) and validates outputs against a comprehensive checklist including a dedicated injection scan. - Use Case: A team with a Playwright + Vitest monorepo asks to set up CI; the Skill detects the fullstack stack, picks GitHub Actions from the git remote, and writes .github/workflows/test.yml with lint, sharded test, burn-in, and report stages plus helper scripts and docs. ## Quick Start Ask the AI 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, selects the CI platform from your git remote, and generates a pipeline with lint, 4-shard parallel test execution, a burn-in loop, and failure artifact uploads. It also creates helper scripts and documentation.

Which CI platforms does this pipeline generator support?

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

What is a burn-in loop in CI testing?

A burn-in loop reruns the test suite multiple times (10 iterations by default) to detect flaky tests before they reach main. It targets UI flakiness, so it is enabled for frontend and fullstack stacks and skipped by default for backend-only projects.

Does it work with backend-only projects in Python, Go, or Java?

Yes. The Skill detects backend stacks via pyproject.toml, go.mod, pom.xml, and similar manifests, then adapts test commands (pytest, go test, mvn test) and caching. Browser install and burn-in stages are omitted for backend-only stacks.

How does it prevent script injection in GitHub Actions workflows?

Generated pipelines never interpolate ${{ inputs.* }} or ${{ github.event.* }} directly in run: blocks. User-controlled values pass through env: intermediaries as quoted variables, and the validation step scans generated YAML for unsafe patterns.

Can I resume an interrupted CI setup workflow?

Yes. The workflow saves progress with frontmatter tracking after each step. Selecting Resume mode loads the progress file, verifies previously created artifacts, and routes to the next incomplete step.