CircleCI
DevToolsCommonly used with
Skills using CircleCI (44)
dep
Handles containerization, CI/CD pipelines, and deployment setup.
release
Generic release assistant — analyzes repo release rules, caches them in .omc/RELEASE_RULE.md, then guides the release
circleci-automation
Automate CircleCI tasks via Rube MCP (Composio): trigger pipelines, monitor workflows/jobs, retrieve artifacts and test metadata. Always search tools first for current schemas.
visual-regression
Setup visual regression testing with Storybook stories, configuration, and CI/CD workflows. Supports Chromatic, Percy, BackstopJS. Auto-invoke when user says "set up visual regression", "add Chromatic tests", "add screenshot testing", or "set up Percy".
ci
Detect/generate/debug CI pipeline config (GitHub Actions, GitLab CI). Triggers: CI setup, build pipeline, GitHub Actions config, debug CI, GitLab CI.
cicd-security
CI/CD pipeline security hunting — GitHub Actions workflow injection, secret exfiltration, self-hosted runner poisoning, dependency confusion, OIDC token theft, and supply chain attacks. Covers sisakulint scanning, manual workflow analysis, and chaining CI/CD bugs into critical findings. Use when a target has public repos, GitHub Actions, CircleCI, Jenkins, or GitLab CI.
playwright-ci
Production-ready CI/CD configurations for Playwright — GitHub Actions, GitLab CI, CircleCI, Azure DevOps, Jenkins, Docker, parallel sharding, reporting, code coverage, and global setup/teardown.
playwright-skill
Battle-tested Playwright patterns for E2E, API, component, visual, accessibility, and security testing. Covers locators, fixtures, POM, network mocking, auth flows, debugging, CI/CD (GitHub Actions, GitLab, CircleCI, Azure, Jenkins), framework recipes (React, Next.js, Vue, Angular), and migration guides from Cypress/Selenium. TypeScript and JavaScript.
cicd-integration
Generate CI pipeline files and check scripts (GitHub Actions, GitLab, CircleCI, Bitbucket) that automate design system checks: token validation, hardcoded values, a11y scans, visual regression, bundle size. Trigger: set up CI, quality gates, automate these checks. Not for running an audit.
guard
Install procoder as a pre-commit hook and a CI check so the gate holds without the agent. Use when the user says "procoder guard", "add procoder to CI", "pre-commit hook", "enforce procoder in CI", "enforce procoder without the agent", or invokes /procoder:guard. Writes files, but only after naming them and getting a yes.
loom-ci-cd
Designs and implements CI/CD pipelines for automated testing, builds, deployment, and security scanning.
migrate-to-teamcity
Migrating CI/CD pipelines to TeamCity. Use when the user wants to migrate, convert, or switch to TeamCity from GitHub Actions (.github/workflows/) or Bamboo (bamboo-specs/*.yml), even if they only say "move our CI". Other CI systems (GitLab, Jenkins, CircleCI, Azure DevOps, Travis, Bitbucket) are not supported yet.
playwright-ci
Production-ready CI/CD configurations for Playwright — GitHub Actions, GitLab CI, CircleCI, Azure DevOps, Jenkins, Docker, parallel sharding, reporting, code coverage, and global setup/teardown.
build-ci-migration-assistant
Automatically migrates build systems and CI/CD configurations to target platforms. Use when modernizing build infrastructure, switching CI/CD providers, or standardizing across projects. Supports common migration paths including Maven↔Gradle, npm↔Yarn, Travis CI→GitHub Actions, CircleCI→GitHub Actions, Jenkins→GitLab CI, and GitLab CI→GitHub Actions. Analyzes existing configuration, generates equivalent target configuration, maps dependencies and commands, and provides validation and migration documentation.
configuration-generator
Generate configuration files for applications, services, and infrastructure. Use when: (1) Setting up new projects (package.json, requirements.txt, tsconfig.json), (2) Creating Docker or Kubernetes configurations, (3) Configuring CI/CD pipelines (GitHub Actions, GitLab CI, CircleCI), (4) Setting up web servers (Nginx, Apache), (5) Defining infrastructure as code (Terraform, CloudFormation), (6) Generating linter/formatter configs (ESLint, Prettier, Black). Provides templates and custom-generated configs for diverse tech stacks.
hatch3r-ci-pipeline
Designs and optimizes CI/CD pipelines. Covers stage design, test parallelization, artifact management, and pipeline performance.
build-ci-cd-pipeline
Design and implement multi-stage CI/CD pipelines using GitHub Actions with matrix builds, dependency caching, artifact management, and secret handling. Create workflows that span linting, testing, building, and deployment stages with parallel execution and conditional logic. Use when setting up automated testing and deployment for a new project, migrating from Jenkins or CircleCI to GitHub Actions, implementing matrix builds across platforms, adding build caching, or creating multi-stage pipelines with security scanning and quality gates.
cicd
CI/CD pipeline design. GitHub Actions, GitLab CI, CircleCI, Jenkins, stage optimization, caching strategies, artifact management, matrix builds, pipeline templating.
devsecops
DevSecOps pipeline security. SAST/DAST/SCA scanning, secret scanning, container scanning (Trivy, Snyk, Semgrep, CodeQL), security gates, shift-left CI/CD integration.
ci-audit
CI/CD pipeline audit for speed, cost, reliability, and security. 10 dimensions (CI1-CI10): caching, parallelism, conditional execution, artifacts, secret handling, action pinning, timeouts, Docker optimization, test integration, and pipeline speed. Primary support: GitHub Actions. Detection-level: GitLab CI, CircleCI. Switches: zuvo:ci-audit full | [path] | --speed-only | --security-only
cicd_integration
CI/CD pipeline interaction — trigger, status check, artifact retrieval.
code-review-cicd
Review CI/CD pipelines for security flaws — poisoned workflows, secret leakage, and injection. Load on GitHub Actions / GitLab CI / Jenkins config, ".github/workflows", pull_request_target, self-hosted runners, or "pipeline security". Signals: workflow YAML, secrets in CI, third-party actions.
keel
Measure whether a codebase's verification actually touches the world, or whether it is checking itself. Keel gathers the verification edges it can read in a target (GitHub Actions, CircleCI, GitLab CI, Travis, package scripts, Makefile, Rakefile, pyproject and a dozen tool configs) — and reports the surfaces it recognised but could not parse, so blindness never passes for absence. It classifies each edge as anchored, self-referential, or unknown by asking whether the actor being verified can write to the signal's producer, and reports a grounding ratio. Novel cases are judged by the agent and then crystallized into probes — small reviewable scripts — so repeat shapes get cheaper every run. Then routes each ungrounded check to an anchored signal that already exists in the same graph. Use when: (1) auditing whether AI-generated or agent-maintained work is genuinely verified, (2) assessing how AI-native a codebase actually is — measured by what fraction of its verification the agents cannot author, (3) reviewing
xcode-cloud
Xcode Cloud CI/CD configuration, workflows, custom scripts, testing, deployment, and optimization. Use when setting up or troubleshooting Xcode Cloud pipelines.
running-quality-checks
Mechanical verification procedure for the verifier agent — detect available checks from project configuration, run them fastest-first in speed order, capture evidence, and derive a PASS/FAIL verdict. Loaded when pre-completion quality checks need to run.
ci-setup
Configure CI/CD pipelines for GitHub Actions, GitLab CI, CircleCI with best practices
ci-qa-gate
Designs, reviews, and configures a quality gate in a CI/CD pipeline — what should actually block a merge and a deploy (lint/format/types, unit+integration tests, coverage threshold on the diff, static analysis/SAST, dependencies/SCA, secret-scan, E2E/smoke, migrations, IaC scan), verifying that the gate really fails the build and does not just warn, that feedback is fast and fail-fast, that flaky tests do not block falsely, and that the pipeline itself is secure (script injection, pinned action versions, minimal token permissions). Use when asked "set up a quality gate", "add tests/lint/coverage to CI", "what should block a merge", "review the pipeline for QA gates", "a gate on coverage/security", "pre-merge checks", "make it so red tests can't be merged", "check our CI for holes in the gates" — even without the word "gate", when they say "why do failing tests get into main", "let's tighten the checks before deploy", "set up pre-commit/pre-push". The skill first detects the project's CI system from its config
devops-commander
Activates the DevOps-Commander agent for infrastructure, CI/CD, and cloud operations. Use when you need GitHub Actions or GitLab CI pipeline design, Dockerfile and docker-compose configuration, Kubernetes deployment manifests, Terraform/Pulumi infrastructure as code, Prometheus + Grafana monitoring setup, or incident response runbooks. Outputs complete, production-ready configuration files.
craft-infra
The Craftsman standard for production infrastructure — deployment, env/config, CI/CD, IaC, health/readiness, scaling, platform/edge rate limiting, build/release, rollback. Use WHENEVER work touches infra: deploy, CI gates, env vars, IaC, load failures, platform rate limiting, pooling runtime constraints, or production runtime. Trigger on "deploy this", "set up CI", "add rate limiting", "configure env vars", or "why did it fall over under load". Owns the platform layer — see "Scope boundaries" in the body for handoffs to craft-backend, craft-security, craft-db, craft-testing, and craft-observability.
craft-infra
The Craftsman standard for production infrastructure — deployment, env/config, CI/CD, IaC, health/readiness, scaling, platform/edge rate limiting, build/release, rollback. Use WHENEVER work touches infra: deploy, CI gates, env vars, IaC, load failures, platform rate limiting, pooling runtime constraints, or production runtime. Trigger on "deploy this", "set up CI", "add rate limiting", "configure env vars", or "why did it fall over under load". Owns the platform layer — see "Scope boundaries" in the body for handoffs to craft-backend, craft-security, craft-db, craft-testing, and craft-observability.
gh-fix-ci
Diagnose failing GitHub Actions checks on a PR via gh, summarize the failure context, propose a plan, and only implement after explicit user approval. External CI providers (Buildkite, CircleCI, etc.) are reported by URL only.
platform-builder-agent
Platform-engineering playbook — Docker/Compose, CI/CD pipelines, Kubernetes, cloud + IaC, monitoring, and the deployment traps that break shipping. Use when the task is containerizing an app, writing a Dockerfile or docker-compose, building a GitHub Actions / GitLab CI pipeline, authoring Kubernetes manifests (Deployment/Service/Ingress/HPA), choosing a deployment target (VPS vs ECS/Cloud Run vs K8s vs serverless), setting up health checks, secrets, autoscaling, backups, or monitoring/observability.
ci-test-orchestration
When the user wants to design, audit, or optimize how tests run in CI — sharding, matrix builds, parallelism, retry policy, test selection, artifact handling, and gate strategy. Use when the user mentions "CI test orchestration," "test sharding," "matrix builds," "parallel tests in CI," "GitHub Actions matrix," "GitLab CI parallel," "Buildkite parallelism," "test selection," "test impact analysis," "CI retries," "test artifacts," or "speeding up CI." For environment specifics see test-environment-management. For cloud-grid mobile/browser see cloud-test-grids. For Grid see selenium-grid.
test-reporting
When the user wants to design, integrate, or improve test reporting — JUnit XML aggregation, HTML dashboards, Allure, Cucumber Reports, screenshots / videos / traces, failure triage, and historical analytics. Use when the user mentions "test reports," "JUnit XML," "Allure," "mochawesome," "Cucumber Reports," "Datadog CI Visibility," "Buildkite Test Analytics," "test result aggregation," "trace / artifacts on failure," "test dashboard," or "trend analysis." For CI orchestration see ci-test-orchestration. For flake analytics see flaky-test-management.
dependency-versions
MUST consult this skill before answering whenever the user's task involves external versioned dependencies — even if you think you can handle it directly. This applies to: checking if packages/tools are up to date, upgrading npm/pip/cargo/go dependencies, writing or reviewing CI/CD (GitHub Actions, CircleCI, GitLab CI), pinning action versions, reviewing Dockerfiles/base images, checking Terraform providers/modules for drift, reviewing Helm chart versions, verifying Kubernetes/EKS/cloud versions, updating pre-commit hooks, writing Dependabot configs, or any task mentioning specific version numbers, package names, or config files like package.json, pyproject.toml, Dockerfile, .pre-commit-config.yaml, main.tf, or values.yaml. Even casual asks like "is this still current" or "has anything drifted" require it — training data is unreliable for volatile version facts. Do NOT use for refactoring code, writing tests, debugging errors, designing APIs, or tasks with no external versioned dependencies.
ci-cd-pipeline-builder
Builds CI/CD pipelines with build, test, security scan and deploy stages across common providers. Use when setting up or repairing a pipeline. Not for infrastructure itself - use iac-provisioner.
github-ci-fix
Fix failing PR checks, debug GitHub Actions, or account for CI follow-up rounds and wait for verification.
speckit-brownfield-scan
Auto-discover project structure, tech stack, frameworks, and architecture patterns
devops-engineer
⚠️ ALWAYS load `docker-skill.md` FIRST when ANY container/Docker work begins, `gameci-unity.md` when ANY Unity CI work begins, and `terraform-skill.md` when ANY Terraform/OpenTofu/IaC work begins. Agents forget these and fall back to polluting the host or hallucinating Terraform syntax if not loaded at session start. DevOps Engineer for Solaris (provider-neutral). CI/CD (GitHub Actions primary + GitLab + CircleCI + Bitrise + Codemagic), IaC (Terraform + OpenTofu + Pulumi + CDK), cloud deploy planning (AWS/GCP/Azure/Vercel/Railway/Fly.io), Kubernetes + Docker, secrets management, observability, release management, incident response, cost optimization. Never silent-deploys production, commits secrets, or force-pushes history.
ci-check
Check a CUBRID PR's CI and, when a test job failed, work out whether it is your change, a project-wide failure, or a flaky test. Reads the PR's checks, pulls the failing tests from CircleCI, and classifies each one against recent runs of the same job on other PRs: 공통 (fails elsewhere too, not yours), flaky (result flips between runs), 고유 (fails only here). Also reports how far the PR's base is behind develop, and shows the failure output for the PR-specific ones. Answers 're-run, update the base, or actually investigate?'. Analysis only: it does not re-run CI or push anything. Triggers on phrases like 'CI 왜 깨졌어', 'CI 실패 원인 확인', '이 PR CI 확인해줘', 'flaky인지 봐줘', '재실행하면 되는지 확인', 'why did CI fail on this PR'.
dep
Handles containerization, CI/CD pipelines, and deployment setup.
init
Set up the QA framework in a project. Works out the stack, writes qa.config.yml, and drops in a CI file. Use when starting on a repo that has no qa.config.yml, when qa-context says no config was found, or when the user says set this up, init, or wire this in.
senior-devops-sre
Use when building or fixing CI/CD pipelines, designing deploy / rollback / canary / blue green strategies, configuring observability (metrics, logs, traces, alerts, SLOs, dashboards), responding to a production incident, writing a runbook, planning capacity, or hardening the platform. Triggers: deploy, deployment, pipeline, CI, CD, GitHub Actions, GitLab CI, CircleCI, Docker, rollout, rollback, canary, blue green, observability, metrics, logs, traces, Prometheus, Grafana, Datadog, alert, SLO, SLI, error budget, incident, postmortem, runbook, on call, paged. Produces pipeline configs, rollout plans, runbooks, dashboards, postmortems. Not for application code, see senior-backend-engineer / senior-frontend-engineer. Not for authoring Terraform / Pulumi / CDK modules, see terraform-expert. Not for Kubernetes manifest authoring, see kubernetes-expert.
ci-cd
Use when the user asks to create, edit, debug, or optimize CI/CD pipelines, workflow YAML, build/test jobs, deployment automation, matrix builds, caches, permissions, or secrets in GitHub Actions, GitLab CI, CircleCI, Jenkins, or similar systems.
Integration detected automatically from skill content. Some results may be false positives.