What problem does it solve? Setting up a production-grade CI/CD pipeline for automated testing is repetitive and error-prone, requiring correct sharding, caching, flaky-test detection, and platform-specific YAML syntax across GitHub Actions, GitLab CI, Azure DevOps, Jenkins, Harness, and Circle CI. ## Core Features & Use Cases - Multi-Platform Pipeline Generation: Produces ready-to-commit CI configuration for GitHub Actions, GitLab CI, Azure DevOps, Jenkins, Harness, or Circle CI from built-in templates. - Test Optimization Patterns: Configures parallel sharding (4 shards by default), dependency and browser caching, failure-only artifact uploads, and a 10-iteration burn-in loop for flaky test detection. - Stack-Aware Adaptation: Auto-detects frontend, backend, fullstack, or mobile stacks and frameworks (Playwright, Cypress, Jest, Vitest, pytest, and more) and adjusts commands, browser installs, and stages accordingly. - Use Case: A team with a Playwright E2E suite asks the agent to set up CI; the skill detects the stack, writes .github/workflows/test.yml 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.