generating-quality-gate-workflows

Generates CI quality gate workflows for GitHub Actions and GitLab CI.

113|17|Updated Oct 5, 2025

Search Tags:#code quality #github actions #quality gates #gitlab ci #ci #branch protection #diff coverage

One-click install

npx skills add https://github.com/jaktestowac/awesome-copilot-for-testers --skill generating-quality-gate-workflows-jaktestowac

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: generating-quality-gate-workflows
Source: https://github.com/jaktestowac/awesome-copilot-for-testers/tree/main/plugins/generating-quality-gate-workflows/skills/generating-quality-gate-workflows
Command: npx skills add https://github.com/jaktestowac/awesome-copilot-for-testers --skill generating-quality-gate-workflows-jaktestowac

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Agreed quality practices often go unenforced: CI either runs everything on every commit until people stop gating on it, or contains steps that cannot fail (`|| true`, `continue-on-error`, non-required checks) so the build reports green regardless. This Skill turns a quality contract into CI that actually enforces it. ## Core Features & Use Cases - Layered gate design: Assigns practices to local hooks, blocking PR jobs, review jobs, and release gates based on feedback speed. - Per-practice CI jobs: Provides working GitHub Actions and GitLab CI job definitions for lint, typecheck, unit tests, diff coverage, E2E sharding, SAST, secret scanning, dependency audit, mutation testing, and evals. - Enforcement wiring: Covers branch protection required checks, sticky PR comments, soft gates via `continue-on-error`/`allow_failure`, fork-safe secret handling, and waiver expiry governance. - Use Case: A team has an agreed quality contract but a green build that never fails. Use this Skill to generate a GitHub Actions workflow with blocking lint, typecheck, and diff-coverage jobs, wire them as required checks, and verify each gate can actually fail. ## Quick Start Generate a GitHub Actions quality gate workflow that enforces our agreed lint, typecheck, unit test, and diff coverage practices as required PR checks.

Frequently Asked Questions about generating-quality-gate-workflows

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

FAQPage Schema

How do I enforce quality gates in GitHub Actions pull requests?▼

Create blocking jobs for lint, typecheck, tests, and diff coverage, then add them as required status checks in branch protection. A job outside branch protection is advisory only, so wiring required checks is the step that makes enforcement real.

How do I set up diff coverage checks in CI?▼

Run tests with coverage, then use diff-cover against the merge base with a fail-under threshold. Fetch full history with fetch-depth 0 and guard against an empty changed-file set, since a shallow clone or broken path matching silently produces a green check.

GitHub Actions vs GitLab CI for soft quality gates?▼

GitLab has a first-class soft gate via allow_failure, which renders amber in the merge request. GitHub Actions uses continue-on-error for the same effect. Both are preferable to `|| true`, which makes a failing check report green.

Why does my CI quality gate always pass even when checks fail?▼

Common causes are `|| true` on commands, thresholds set below current values, jobs missing from required checks, or shallow clones breaking diff-based checks. Verify each gate by deliberately breaking what it checks on a scratch branch and confirming it goes red.

How do I handle secrets in CI for fork pull requests?▼

Skip secret-dependent jobs on forks using a condition on the head repository, and run a key-free subset instead. Use pull_request rather than pull_request_target for anything executing PR code, and pass untrusted input through env variables to avoid shell injection.