Quality gate procedures - build/type/lint/test pipeline, auto-fix loop, changes signaling

Run build, type-check, lint, test, and security pipeline with auto-fix loop.

1|1|Updated Feb 1, 2026
One-click install
npx skills add https://github.com/zb-ss/claude-plugin-workflow --skill quality-gate-procedures-build-type-lint-test-pipeline-auto-fix-loop-changes-signaling
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Quality gate procedures - build/type/lint/test pipeline, auto-fix loop, changes signaling
Source: https://github.com/zb-ss/claude-plugin-workflow/tree/main/skills/phases/quality-gate
Command: npx skills add https://github.com/zb-ss/claude-plugin-workflow --skill quality-gate-procedures-build-type-lint-test-pipeline-auto-fix-loop-changes-signaling

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents broken builds and unreliable releases by running a consistent build/type/lint/test pipeline, auto-fixing fixable failures, and detecting critical regressions early.

Core Features & Use Cases

  • Sequential quality pipeline: Runs build, type checks, lint, tests, full regression tests, and security audit in a defined order, stopping at the first failure to reduce noise.
  • Auto-fix loop with bounded attempts: Reads error output, applies fixes, and re-runs checks up to a maximum of three attempts per failing step.
  • Change signaling for targeted review: Emits a CHANGES_MADE block listing changed files to trigger focused downstream review of modified areas.
  • Strict PASS/FAIL verdicts: Produces clear VERDICT outputs including failure details and whether changes were made.

Quick Start

Use the quality gate to run your project through build, type, lint, full tests, regression tests, and security audit, auto-fixing up to three times per failing check and reporting a PASS or FAIL verdict.

Frequently Asked Questions about Quality gate procedures - build/type/lint/test pipeline, auto-fix loop, changes signaling

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

FAQPage Schema
How do I run a build, type check, and lint pipeline that stops on the first failure?

A sequential quality pipeline executes build, type checks, lint, tests, regression tests, and security audit in a defined order, stopping at the first failure to reduce noise and isolate issues quickly.

Can I auto-fix linting and type checking errors automatically during continuous integration?

An auto-fix loop reads error output, applies fixes, and re-runs checks up to a maximum of three attempts per failing step to recover from fixable failures automatically.

Does the quality gate pipeline work with Python and PHP projects or only TypeScript?

The pipeline applies to TypeScript, JavaScript, PHP, and Python projects, running CI-like verification and quick recovery from fixable failures across these language environments.

What's the best way to detect regressions and track changed files after automated fixes?

Change signaling emits a CHANGES_MADE block listing changed files to trigger focused downstream review, while requiring a full regression test re-run before reporting a final PASS verdict.

Why does my quality gate report FAIL even after auto-fixing build and test errors?

Strict PASS/FAIL verdicts require a full regression re-run after any auto-fix changes, ensuring no new regressions were introduced before a PASS verdict is reported.

How do I enforce bounded fix attempts for failing CI checks without infinite loops?

The auto-fix loop enforces bounded fix attempts by applying fixes and re-running checks up to a maximum of three times per failing step, preventing infinite loops and signaling failure.