CircleCI
DevToolsCommonly used with
Skills using CircleCI (19)
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.
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.
ci
Detect/generate/debug CI pipeline config (GitHub Actions, GitLab CI). Triggers: CI setup, build pipeline, GitHub Actions config, debug CI, 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.
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.
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
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.
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.
xcode-cloud
Xcode Cloud CI/CD configuration, workflows, custom scripts, testing, deployment, and optimization. Use when setting up or troubleshooting Xcode Cloud pipelines.
ci-setup
Configure CI/CD pipelines for GitHub Actions, GitLab CI, CircleCI with best practices
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.
github-ci-fix
Use when PR checks fail, CI is red, or GitHub Actions workflows break - systematically inspects failing checks via gh CLI, pulls logs, checks for flakiness and scopes the breaking commit, scopes external checks, then creates fix plan using existing plan skill
dep
Handles containerization, CI/CD pipelines, and deployment setup.
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.
Integration detected automatically from skill content. Some results may be false positives.