ci

Design and validate CI workflows for spec-driven repositories.

3|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/xiongxianfei/rigorloop --skill ci-xiongxianfei
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ci
Source: https://github.com/xiongxianfei/rigorloop/tree/main/.codex/skills/ci
Command: npx skills add https://github.com/xiongxianfei/rigorloop --skill ci-xiongxianfei

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

CI design and review often lag, causing unvalidated changes to slip into PRs and slow down delivery. This skill provides a structured approach to authoring and validating CI workflows that align with project conventions and risk.

Core Features & Use Cases

  • Define PR-focused CI workflows that validate changes before merge.
  • Configure deterministic, fast feedback with proper triggers, path filters, and caching.
  • Provide ready-to-use review gates and quality checks for feature verification.

Quick Start

Define a new PR validation workflow by creating a GitHub Actions file and tailoring it to your repo's conventions.

Frequently Asked Questions about ci

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

FAQPage Schema
How do I configure GitHub Actions CI workflows for PR validation?▼

To configure GitHub Actions CI workflows for PR validation, you define an on.pull_request configuration with path filters and caching to ensure deterministic, fast feedback across multiple languages before merging.

What is the best way to structure CI workflows for spec-driven repositories?▼

Structuring CI workflows for spec-driven repositories involves specifying naming conventions, on.pull_request configuration, path filters, caching, and guardrails to ensure reliable, auditable feature verification results.

Does this CI workflow approach support multiple languages and testing tools?▼

Yes, this CI workflow approach supports multiple languages and tools, providing ready-to-use review gates and quality checks for fast feedback across your spec-driven repositories.

Why do unvalidated changes slip into PRs during CI design and review?▼

Unvalidated changes slip into PRs because CI design and review often lag, but applying structured PR-focused workflows with deterministic triggers and guardrails prevents this and accelerates delivery.

Can I use path filters and caching to speed up GitHub Actions CI feedback?▼

Yes, you can use path filters and caching to configure deterministic, fast feedback in GitHub Actions CI workflows tailored to your repo's conventions and risk.