ci-verify

Queue open PRs into a testing branch and run tiered verification gates.

Updated Feb 3, 2026
One-click install
npx skills add https://github.com/BedaBeda-Growth/bedabeda-growth-site --skill ci-verify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ci-verify
Source: https://github.com/BedaBeda-Growth/bedabeda-growth-site/tree/main/skills/ci-verify
Command: npx skills add https://github.com/BedaBeda-Growth/bedabeda-growth-site --skill ci-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of handling open PRs by merging them sequentially into a testing branch, running layered verification, and optionally spawning parallel subagents to pre-check branches before merging to main.

Core Features & Use Cases

  • Discover open PRs, prioritize by signals, perform sequential merges with verification, fix failures inline, and report results. Optional parallel fan-out for large backlogs where 10+ PRs are processed.

Quick Start

Run the main merge-and-verify script to begin processing open PRs on the testing branch.

Frequently Asked Questions about ci-verify

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

FAQPage Schema
How do I automate PR verification for a large backlog of open pull requests?

Automated PR verification discovers open PRs, prioritizes them by signals, sequentially merges them into a testing branch, and runs layered verification gates before reporting results. This handles large backlogs through staged validation without manual intervention.

What is a testing branch workflow for staged PR validation?

A testing branch workflow merges open PRs sequentially into an isolated testing branch, runs tiered verification gates, and then queues validated changes for a governed merge to main. It ensures staged validation and branch ancestry checks before final integration.

Can I run parallel checks on multiple PRs before merging to main?

Yes, parallel subagents can fan out to pre-check branches before merging to main. This optional feature applies to large PR backlogs where 10 or more PRs require processing, enabling concurrent pre-verification.

How do I prioritize and queue pull requests for sequential merging and testing?

PR prioritization applies rules based on signals to queue open PRs for sequential merging into a testing branch. The queue governs the merge process to main, applying ancestry checks and tiered verification gates at each stage.

Does the automated merge queue handle failures inline during the verification process?

Yes, the automated merge and verify process fixes failures inline during sequential merges. It runs layered verification gates after each merge, addresses failures, and outputs a JSON report of the final results.

When should I use a governed merge queue instead of standard continuous integration?

A governed merge queue suits large PR backlogs requiring staged validation, ancestry checks, and tiered verification gates. Standard CI lacks sequential merging, inline failure fixing, and parallel subagent pre-checks needed for processing 10 or more PRs.