cicd-quality

What problem does it solve?

CI/CD teams often struggle to enforce consistent quality across pipelines. This skill provides a framework to design and implement automated quality gates that block unsafe changes from reaching production, ensuring every commit is tested, scanned, and validated before deployment.

Core Features & Use Cases

• Gate 1: Code Quality: Linting, formatting, type checking to prevent low-quality code from entering main branches.
• Gate 2: Tests: Unit and integration tests with coverage gates to ensure reliable functionality.
• Gate 3: Security: Dependency audits, secret scanning, and SAST checks to uncover vulnerabilities.
• Gate 4: Build: Compile and containerization steps ensuring a reproducible artifact.
• Gate 5: E2E: End-to-end tests for critical user flows to catch regressions.
• Gate 6: Performance Budget: Enforce bundle size and performance budgets.

Quick Start

Configure your CI/CD pipelines to include the above gates and run them on PRs and pushes to main or dev branches.