ci-quality-gate

Automate CI quality gate checks after code execution.

1|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/gonz0w/bgsd-oc --skill ci-quality-gate
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ci-quality-gate
Source: https://github.com/gonz0w/bgsd-oc/tree/main/skills/ci-quality-gate
Command: npx skills add https://github.com/gonz0w/bgsd-oc --skill ci-quality-gate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a standard CI quality gate block used after plan/execution to verify CI is enabled, present a gate header, spawn the CI agent with proper parameters, and handle merged or checkpoint outcomes.

Core Features & Use Cases

  • Displays a gate header and checks the CI configuration to ensure the gate will run.
  • Spawns the bgsd-github-ci agent with parameterized branch and scope to perform code scanning.
  • Handles merged and checkpoint results to either advance or pause the workflow.

Quick Start

Use the ci-quality-gate block after execution, providing a scope (e.g., phase-1) and a base_branch (e.g., main) to enable automated code-scanning.

Frequently Asked Questions about ci-quality-gate

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

FAQPage Schema
How do I enforce CI quality gates automatically after code execution?▼

A CI quality gate validates changes by running automated code-scanning after execution. It spawns a CI agent with parameterized branch and scope, interpreting merged or checkpoint outcomes to advance or pause the workflow before merging.

What does a CI quality gate check after a workflow execution?▼

A CI quality gate checks CI configuration and performs code-scanning to validate changes. It spawns a CI agent with parameterized branch and scope, interpreting merged or checkpoint outcomes to advance or pause the workflow.

Can I use automated CI gating for phase-based workflows with a specific base branch?▼

Yes, automated CI gating supports phase-based workflows by accepting a scope and base_branch. The gate spawns a CI agent with parameterized branch and scope to perform code-scanning and validate changes before merging.

How do I handle merged or checkpoint outcomes when automating CI checks?▼

Handling merged or checkpoint outcomes involves interpreting CI code-scanning results to advance or pause the workflow. The gate evaluates whether changes are validated by CI before allowing the workflow to proceed or merge.

Do I need to manually trigger code-scanning for post-execution CI gating?▼

No, post-execution CI gating automates code-scanning by spawning a CI agent automatically. The gate block handles CI parameters and performs validation without manual intervention after execution.

Why does my workflow pause after running automated CI quality gate checks?▼

Your workflow pauses after CI quality gate checks because the gate interpreted a checkpoint outcome or failed code-scanning results. It pauses the workflow to prevent merging unvalidated changes before CI requirements are met.