cicd-quality

Design and enforce CI/CD quality gates for code, tests, security, build, E2E, and performance.

3|Updated May 28, 2026
One-click install
npx skills add https://github.com/mahg-es/araya --skill cicd-quality
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cicd-quality
Source: https://github.com/mahg-es/araya/tree/main/skills/cicd-quality
Command: npx skills add https://github.com/mahg-es/araya --skill cicd-quality

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about cicd-quality

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up CI/CD quality gates to block unsafe changes from reaching production?

To set up CI/CD quality gates, configure your automated pipelines to run code quality, testing, security, build, E2E, and performance checks on pull requests and branch pushes, blocking merges when requirements are unmet.

What is the best way to enforce consistent code quality and security across automated pipelines?

The best way to enforce consistent code quality and security is by implementing configurable gate definitions with thresholds for linting, dependency audits, and SAST checks to block unsafe commits before deployment.

Can I configure specific thresholds for testing and performance budgets in my CI/CD pipelines?

Yes, you can configure specific thresholds for testing and performance budgets. The framework implements configurable gate definitions to enforce bundle size limits and test coverage requirements across your pipelines.

Does this CI/CD quality gate framework support end-to-end testing and secret scanning?

Yes, the CI/CD quality gate framework supports end-to-end testing and secret scanning. It includes dedicated E2E gates for critical user flows and security gates for uncovering vulnerabilities in dependencies.

How do I provide clear failure messaging when a pipeline quality gate blocks a merge?

To provide clear failure messaging when a pipeline quality gate blocks a merge, the framework implements configurable gate definitions that output explicit failure reasons, ensuring developers understand exactly which requirements failed.