What problem does it solve? Setting up a CI/CD pipeline for automated testing requires platform-specific YAML syntax, sharding strategies, flaky-test detection, and security hardening that teams often get wrong or skip entirely. ## Core Features & Use Cases - Multi-Platform Pipeline Generation: Produces ready-to-adapt pipeline configs for GitHub Actions, GitLab CI, Azure DevOps, Harness, Jenkins, and Circle CI with lint, test, burn-in, and report stages. - Stack-Aware Test Execution: Auto-detects frontend, backend, fullstack, or mobile stacks and configures the right test commands, browser installs, caching, and parallel sharding. - Quality Gates & Security: Adds burn-in loops for flaky test detection, pass-rate thresholds, optional Pact contract-testing stages, and enforces script-injection-safe patterns for reusable workflows. - Use Case: A team with a Playwright E2E suite asks to set up CI; the skill detects the stack, generates a GitHub Actions workflow with 4-way sharding and a weekly burn-in cron, scaffolds helper scripts, and writes docs/ci.md with a secrets checklist. ## Quick Start Ask the assistant to set up a CI pipeline with quality gates for this repository and let it detect the platform and test framework automatically.