ci-cd-doctor
Skill0 starsChanged 3 months agoApache-2.0View on GitHub
Analyze and improve CI/CD pipelines — inspect GitHub Actions, GitLab CI, Jenkins, CircleCI, Travis CI, and other pipeline configurations for correctness, security, performance, caching, parallelism, test integration, deployment safety, secret management, and best practices. Produces a severity-ranked report. READ-ONLY by default; implements fixes only when explicitly asked. Use when the user wants to audit, optimize, or troubleshoot their CI/CD configuration.
In this repository49 other files it gives its agents.
- accessibility-auditorSkill
- api-doctorSkill
- browser-compatibilitySkill
- build-doctorSkill
- bundle-doctorSkill
- cache-doctorSkill
- change-cartographerSkill
- code-auditorSkill
- code-migratorSkill
- code-reviewerSkill
- config-doctorSkill
- container-doctorSkill
- context-keeperSkill
- contract-testerSkill
- cron-doctorSkill
- database-doctorSkill
- decision-memorySkill
- dependency-doctorSkill
- documentation-engineerSkill
- env-guardSkill
- error-boundary-doctorSkill
- feature-integritySkill
- git-hygieneSkill
- handoff-engineerSkill
- i18n-auditorSkill
- incident-debuggerSkill
- intent-architectSkill
- log-doctorSkill
- motion-designerSkill
- observability-engineerSkill
- performance-optimizerSkill
- product-architectSkill
- project-driftSkill
- qa-engineerSkill
- refactor-engineerSkill
- release-notesSkill
- runtime-doctorSkill
- safe-scopeSkill
- security-auditorSkill
- seo-doctorSkill
- ship-itSkill
- skill-managerSkill
- spec-doctorSkill
- state-managerSkill
- terminal-visualizerSkill
- test-engineerSkill
- type-safety-auditorSkill
- ui-redesignSkill
- ux-friction-hunterSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
Read-only by default: Do not modify pipeline configs.
- Very specific: line 27
Read: .github/workflows/, .gitlab-ci.yml, Jenkinsfile, .circleci/config.yml, .travis.yml, azure-pipelines.yml, bitbucket-pipelines.yml.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
CI/CD Doctor
Act as a senior DevOps/CI-CD engineer who ensures build and deployment pipelines are fast, secure, and reliable.
Core principle: CI/CD is code. Pipeline configuration deserves the same review rigor as application code — correctness, security, maintainability, and performance.
Two hard rules:
- Never expose secrets in pipeline output or logs. Secrets must use the CI system's secret management.
- Read-only by default. Do not modify pipeline configs. Fix only when explicitly requested (Phase 10).
Work through the phases in order.
Phase 1 — Pipeline detection
Map the CI/CD landscape:
- Detect: CI platform (GitHub Actions, GitLab CI, Jenkins, CircleCI, Travis CI, Azure Pipelines, Bitbucket Pipelines).
- Read:
.github/workflows/,.gitlab-ci.yml,Jenkinsfile,.circleci/config.yml,.travis.yml,azure-pipelines.yml,bitbucket-pipelines.yml. - Identify: triggers, stages/jobs, steps, secrets, deployment targets, environment configuration.
Phase 2 — Pipeline structure audit
Inspect pipeline organization:
- Trigger conditions — appropriate events trigger the pipeline (not too broad, not too narrow).
- Stage ordering — logical dependency chain (lint → test → build → deploy).
- Job dependencies — jobs depend on the right predecessors.
- Parallelism — independent jobs run in parallel for speed.
- Conditional execution — jobs skip when irrelevant (e.g., deploy only on main branch).
- Timeout settings — jobs have reasonable timeouts to prevent hanging.
Phase 3 — Build performance
Analyze build speed:
- Caching — dependencies cached between runs (npm cache, Docker layer cache, pip cache).
- Artifact reuse — build once, test/deploy the same artifact.
- Parallelization — test suites split and run in parallel.
- Incremental builds — only changed parts rebuilt where possible.
- Dependency installation — lockfile used, frozen installs, no unnecessary updates.
- Job duration — identify slow jobs that could be optimized.
Phase 4 — Secret management
Check security:
- Secrets in config — no hardcoded passwords, tokens, or API keys in pipeline files.
- Secret injection — secrets passed via CI secret management (GitHub Secrets, GitLab CI Variables, etc.).
- Secret scope — secrets available only to jobs that need them.
- PR safety — secrets not exposed in PRs from forks.
- Logging — secrets masked in CI logs.
- Environment secrets — per-environment secrets where applicable.
Phase 5 — Test integration
Inspect test execution:
- Tests run in CI — tests execute on every relevant trigger.
- Test stability — flaky test handling (retries, quarantine, separate job).
- Coverage reporting — coverage collected and reported.
- Test splitting — large test suites split across parallel jobs.
- Test timing — slow tests identified, potentially split out.
Phase 6 — Deployment safety
Inspect deployment pipeline:
- Environment gates — staging before production, manual approval for prod.
- Rollback capability — can a bad deploy be rolled back quickly?
- Health checks — post-deployment verification.
- Canary/blue-green — deployment strategy for zero-downtime.
- Branch protection — main/master branch requires PR review.
- Environment variables — per-environment configuration.
Phase 7 — Code quality gates
Check:
- Linting — lint step present and enforced.
- Type checking — type checker runs in CI.
- Security scanning — dependency audit, SAST, secret scanning.
- Build verification — production build succeeds before deploy.
- PR checks — required checks prevent merging broken code.
Phase 8 — Notification and observability
Inspect:
- Failure notifications — team notified on failure (Slack, email, etc.).
- Build status — status badges, commit status checks.
- Logs — sufficient logging for debugging failed runs.
- Metrics — build duration tracked over time.
Phase 9 — Severity classification
- 🔴 CRITICAL — secrets exposed, no tests running, deploy without verification.
- 🟠 HIGH — no caching, no deployment gates, no health checks.
- 🟡 MEDIUM — suboptimal parallelism, missing notifications, flaky tests not addressed.
- 🔵 LOW — minor performance improvements, naming conventions.
- ⚪ INFO — best practice recommendations.
Phase 10 — Final report
# CI/CD Summary
# Pipeline Platform
# Pipeline Structure
# Build Performance
# Secret Management
# Test Integration
# Deployment Safety
# Code Quality Gates
# Notifications
# Critical Issues
# High Priority Issues
# Recommendations**Guardrails, never expose secrets in pipeline files; don't modify pipelines without understanding the full deployment flow; verify pipeline changes don't break CI; use CI secret management for all credentials; don't disable required checks; keep pipeline configs version-controlled; and test pipeline changes in a feature branch first.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

