What problem does it solve? Setting up a production-grade CI/CD pipeline for automated testing requires platform-specific YAML syntax, flaky-test detection strategies, caching configuration, and security hardening that teams often get wrong or skip entirely. ## Core Features & Use Cases - Multi-Platform Pipeline Generation: Scaffolds CI configurations for GitHub Actions, GitLab CI, Azure DevOps, Jenkins, Harness, and Circle CI from ready-made templates. - Test Optimization Built In: Configures parallel sharding (4 shards by default), dependency caching, burn-in loops for flaky test detection, and failure-only artifact collection. - Security Hardening: Enforces script-injection prevention by routing user-controlled inputs through env intermediaries and validating generated YAML against a security checklist. - 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 lint, sharded test, burn-in, and report stages, plus helper scripts and documentation. ## Quick Start Ask the agent to set up a CI pipeline with quality gates for this repository and let it detect the platform and test framework automatically.
