What problem does it solve? Merge decisions often rest on impression rather than mechanical checks, and teams lack a single policy stating which CI/CD gates run, where they sit in the pipeline, and what thresholds block a merge. This Skill supplies that policy so an agent can prove a change is mergeable with real evidence instead of self-report. ## Core Features & Use Cases - Gate tables per loop model: Specifies which gates are required at staging versus production under gitflow-multi-env, and which block the single PR to main under trunk-single-env. - Concrete thresholds: Enforces lint and typecheck at zero errors, unit coverage at 85% or higher on lines, functions, branches, and statements, plus dependency audit, SAST, secret scanning, and contract or E2E runs. - Merge-class rules: Defines who merges each class of change, including the quality-assurance gatekeeper verdicts and the four surviving human holds. - Use Case: When wiring CI for a new repository or reviewing a merge request, consult this Skill to decide which checks must be required, blocking, and where enforcement lives in hooks versus CI. ## Quick Start Ask the agent to apply the quality-gates policy to decide which CI checks must block the merge of the current pull request.
