Skip to content
OpenAgentSkill
Browsing is open · Catalog captured 2026-11-21 · Automatic updates and account services are paused.
DevOps & cloud

cicd-integration

Generate CI/CD pipeline configurations that automate design system quality checks — token validation, component linting, visual regression, accessibility scanning, and release gating. Produces ready-to-use pipeline files for GitHub Actions, GitLab CI, CircleCI, or Bitbucket Pipelines, configured to enforce the standards that audit skills check manually. Trigger when someone says: set up CI for the design system, automate these checks, add pipeline for tokens, create GitHub Action for design system, CI/CD for components, automate the release process, continuous integration for design system, how do I automate what the audit found, quality gates in CI, or anything about automating design system quality checks in a pipeline. Do NOT trigger for running a manual audit — use the specific audit skill for that. Do NOT trigger for generating a release checklist — use change-communication for that.

murphytrueman · AI review on file

Installation

Read the source and dependencies before running a command. Copying does not install or execute anything.

npx skills add murphytrueman/design-system-ops --skill cicd-integration

About this skill


name: cicd-integration description: "Generate CI/CD pipeline configurations that automate design system quality checks — token validation, component linting, visual regression, accessibility scanning, and release gating. Produces ready-to-use pipeline files for GitHub Actions, GitLab CI, CircleCI, or Bitbucket Pipelines, configured to enforce the standards that audit skills check manually. Trigger when someone says: set up CI for the design system, automate these checks, add pipeline for tokens, create GitHub Action for design system, CI/CD for components, automate the release process, continuous integration for design system, how do I automate what the audit found, quality gates in CI, or anything about automating design system quality checks in a pipeline. Do NOT trigger for running a manual audit — use the specific audit skill for that. Do NOT trigger for generating a release checklist — use change-communication for that." references:

  • ../../knowledge-notes/component-governance.md
  • ../../knowledge-notes/token-architecture.md
  • ../../knowledge-notes/design-to-code-contract.md

CI/CD Integration

A skill for generating pipeline configurations that automate the quality checks Design System Ops skills perform manually. This bridges the gap between "here are the problems the audit found" and "these problems can never recur because the pipeline catches them."

Output type: File creation. This skill produces pipeline configuration files (YAML), scripts, and documentation. It does not execute pipelines — it generates the configuration that teams add to their repository.


Why this exists

Every audit skill in Design System Ops finds problems. Some of those problems should never have reached a human reviewer because they are mechanically detectable: a hardcoded hex value in a component file, a token alias that references a non-existent token, a component export missing from the barrel file, an accessibility violation that an automated scanner would catch.

CI/CD Integration converts audit findings into automated pipeline checks. The goal is not to replace the audit skills — those handle nuance, context, and cross-skill synthesis that pipelines cannot. The goal is to automate the mechanical subset so that audits focus on the problems only humans can evaluate.


Configuration

Check for .ds-ops-config.yml in the project root:

cicd:
  platform: "github-actions"         # github-actions, gitlab-ci, circleci, bitbucket
  package_manager: "npm"              # npm, yarn, pnpm
  node_version: "20"                  # Node.js version
  test_framework: "jest"              # jest, vitest, playwright
  component_library_path: "packages/components"
  token_path: "packages/tokens"
  monorepo: true                      # Whether the project uses a monorepo structure
  triggers:
    - "push to main"
    - "pull request to main"

If no configuration exists, ask for:

  1. CI/CD platform (default: GitHub Actions)
  2. Package manager (default: npm)
  3. Whether the project is a monorepo
  4. Paths to token files and component files

Step 0: Assess what to automate

Before generating any pipeline configuration, determine which checks are worth automating. Not everything should be in CI.

Automation decision matrix

Check typeAutomate in CI?Why
Token naming violationsYesMechanical — regex patterns, no judgment needed
Token circular referencesYesGraph traversal — computers are better at this
Hardcoded colour valuesYesgrep/AST — exact match detection
Component prop type checkingYesTypeScript/Flow already does this
Accessibility (automated subset)Yesaxe-core catches 30–40% of WCAG violations
Visual regressionYesPixel comparison catches unintended changes
Component export completenessYesAST/barrel file check
Bundle size trackingYesByte comparison — pure measurement
Token coverage gapsPartialCan check primitive→semantic mapping exists, cannot judge if mappings are correct
Component API consistencyPartialCan lint prop naming patterns, cannot judge API design quality
Documentation completenessPartialCan check if docs exist, cannot judge if they are good
Cross-component pattern complianceNoRequires too much context and judgment
Naming convention qualityNoConventions need human validation first, then automation
Usage guideline adherenceNoRequires consuming-app context that CI rarely has

Rule of thumb

If the skill's finding includes a specific, unambiguous rule (e.g., "tokens must use kebab-case", "no hex values outside token files"), it can be automated. If the finding requires judgment (e.g., "this token naming could be clearer"), it cannot.


Step 1: Map audit findings to pipeline checks

For each audit finding category, determine the automated check:

Token checks

Finding categoryPipeline checkTool
Naming violationsLint token names against convention regexCustom script or Style Dictionary validator
Circular referencesBuild-time alias resolution checkStyle Dictionary build (fails on circular refs)
Orphaned tokensCross-reference token definitions with usage in component filesCustom script: grep token names across component source
Missing semantic tierCheck that every component token reference resolves through a semantic aliasCustom script or Style Dictionary referencing
DTCG format complianceValidate token files against DTCG schemaJSON Schema validation

Component checks

Finding categoryPipeline checkTool
Export completenessVerify barrel file exports match component directoriesCustom script: compare fs listing with exports
Prop type safetyTypeScript strict mode compilationtsc --noEmit
AccessibilityRun axe-core on rendered components@axe-core/cli, jest-axe,
Read the complete source ↗