bmad-testarch-ci

You can auto-generate CI pipelines by analyzing repository context to select platform-specific templates for GitHub Actions, GitLab CI, or Azure DevOps, tailoring lint, test, burn-in, and shard configurations to your detected stack.

Test sharding splits test suites into parallel segments for faster execution, while burn-in testing runs loops repeatedly to catch flaky failures. Both are automated stages built into the generated CI pipelines to ensure deployment reliability.

Scaffold a multi-stage CI pipeline by stepping through preflight, pipeline generation, and quality gates. The process builds parallel test shards, burn-in loops, and artifact collection stages, finishing with a validation check summarizing configuration readiness.

Yes, adaptable templates support frontend, backend, and fullstack stacks with pluggable framework support. The skill detects your repository context and tailors the CI orchestration configurations to match the specific stack requirements.

The best way to validate configuration readiness is running the built-in validation step, which summarizes pipeline completeness and checks quality gates. This pre-merge validation ensures your lint, test, and sharding configurations are safe for deployment.

CI pipeline generation may fail to detect the correct stack if repository context is ambiguous or unsupported. Ensure your project structure matches recognizable stack patterns so the pluggable templates can properly tailor lint and test configurations.