ci-standards

Validate CI/CD configurations and testing infrastructure in Nx monorepos.

3|1|Updated Apr 18, 2026
One-click install
npx skills add https://github.com/wahidyankf/ose-primer --skill ci-standards
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ci-standards
Source: https://github.com/wahidyankf/ose-primer/tree/main/.claude/skills/ci-standards
Command: npx skills add https://github.com/wahidyankf/ose-primer --skill ci-standards

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of inconsistent CI/CD configurations and non-compliant testing infrastructure across polyglot Nx monorepo projects, which commonly cause broken pipelines, missed coverage requirements, and governance violations.

Core Features & Use Cases

  • Centralized CI Standards: Provides a single source of truth for all CI/CD conventions, including mandatory Nx targets, coverage thresholds, Docker setup rules, E2E pairing requirements, Gherkin test mandates, and workflow scheduling standards.
  • Agent Integration: Used by swe-*-dev agents to set up new projects correctly, and by ci-checker/ci-fixer agents to validate and remediate CI compliance issues.
  • Use Case: A developer setting up a new Rust Axum backend can use this Skill to confirm all required Nx targets and Docker files are present, while a CI checker agent can scan an existing project's pipeline to flag missing coverage thresholds or incorrect workflow schedules.

Quick Start

Use the ci-standards skill to validate that the new crud-be-rust-axum project meets all CI/CD convention requirements including Nx targets, coverage thresholds, and Docker configuration.

Frequently Asked Questions about ci-standards

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

FAQPage Schema
How do I enforce CI/CD compliance standards across an Nx monorepo?

Enforce CI/CD compliance by validating mandatory Nx targets, coverage thresholds, Docker configurations, and E2E test pairing requirements across polyglot Nx monorepo projects to eliminate inconsistent pipeline configurations.

What is the best way to validate testing infrastructure in a polyglot monorepo?

The best way to validate testing infrastructure is to check for Gherkin test mandates, enforce coverage thresholds, and verify E2E test pairing across all backend, frontend, and fullstack project types within the repository.

How do I check if a new project meets repository CI conventions?

Check new project CI conventions by validating CI pipelines against centralized standards, ensuring required Nx targets, Docker files, and scheduled workflows are correctly configured before integration.

Can I use automation agents to fix non-compliant CI pipelines?

Yes, you can use ci-checker and ci-fixer agents to scan existing projects, flag missing coverage thresholds or incorrect workflow schedules, and automatically remediate CI compliance issues across the monorepo.

Does Nx target validation support different project types like Rust or CLI?

Nx target validation supports backend, frontend, fullstack, CLI, and library project types, allowing confirmation of required Docker files and CI targets for polyglot projects like a Rust Axum backend.