How do I install the Execution Cicd Pipeline skill?

Run npx skillmds@latest add deankelly751/execution-cicd-pipeline in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Execution Cicd Pipeline safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Execution Cicd Pipeline?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Execution Cicd Pipeline free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Execution Cicd Pipeline?

DeanKelly751 (@deankelly751) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Execution Cicd Pipeline by deankelly751

Name: Execution Cicd Pipeline
Author: DeanKelly751

Execution Cicd Pipeline

Design a CI/CD pipeline from scratch. Step-by-step procedure covering stage design, artifact management, environment promotion, and failure handling. Use when setting up CI/CD for new projects or improving existing pipelines.

DeanKelly751 Updated Sep 21, 2026

File contents

CI/CD Pipeline Design

Purpose

Step-by-step procedure for designing an effective CI/CD pipeline.

Workflow

Step 1: Define Pipeline Stages

Minimum viable pipeline:

Check (seconds): lint, format, type check
Test (minutes): unit tests, coverage threshold
Build (minutes): compile, package, create artifact
Deploy staging (minutes): deploy to pre-production
Verify (minutes): smoke tests against staging
Deploy production: release to users

Step 2: Optimize for Speed

Parallelize independent steps (lint ‖ test ‖ security scan)
Cache dependencies between runs
Only rebuild/retest what changed (affected tests, monorepo filters)
Fast-fail: cheapest checks first

Step 3: Artifact Management

Build artifact ONCE, deploy the SAME artifact everywhere
Tag artifacts with commit SHA
Store in artifact registry (container registry, package registry)
Promote artifact between environments (don't rebuild)

Step 4: Environment Promotion

PR → [check + test + build] → merge to main → [deploy staging] → [verify] → [deploy prod]

Staging deployment automatic on merge
Production deployment: automatic (CD) or gated (approval)
Same configuration shape across environments (different values via env vars)

Step 5: Failure Handling

Flaky test quarantine (track and isolate, don't block pipeline)
Automatic rollback on health check failure post-deploy
Notifications to PR author on failure
Pipeline run logs accessible and searchable

Checklist

All checks pass before merge allowed
Artifact built once, promoted through environments
Dependencies cached for speed
Independent stages parallelized
Deployment to staging automatic on merge
Smoke/health tests verify each deployment
Rollback mechanism defined and tested
Secrets injected at runtime, never in pipeline config
Pipeline completes in <10 minutes for feedback loop

Related Skills

deployment/knowledge-cicd-principles — philosophy behind the pipeline
deployment/execution-git-workflow — branch strategy feeding the pipeline
infrastructure/execution-containerization — building container artifacts

---name: execution-cicd-pipelinedescription: Design a CI/CD pipeline from scratch. Step-by-step procedure covering stage design, artifact management, environment promotion, and failure handling. Use when setting up CI/CD for new projects or improving existing pipelines.---# CI/CD Pipeline Design## PurposeStep-by-step procedure for designing an effective CI/CD pipeline.## Workflow### Step 1: Define Pipeline StagesMinimum viable pipeline:1. **Check** (seconds): lint, format, type check2. **Test** (minutes): unit tests, coverage threshold3. **Build** (minutes): compile, package, create artifact4. **Deploy staging** (minutes): deploy to pre-production5. **Verify** (minutes): smoke tests against staging6. **Deploy production**: release to users### Step 2: Optimize for Speed- Parallelize independent steps (lint ‖ test ‖ security scan)- Cache dependencies between runs- Only rebuild/retest what changed (affected tests, monorepo filters)- Fast-fail: cheapest checks first### Step 3: Artifact Management- Build artifact ONCE, deploy the SAME artifact everywhere- Tag artifacts with commit SHA- Store in artifact registry (container registry, package registry)- Promote artifact between environments (don't rebuild)### Step 4: Environment Promotion```PR → [check + test + build] → merge to main → [deploy staging] → [verify] → [deploy prod]```- Staging deployment automatic on merge- Production deployment: automatic (CD) or gated (approval)- Same configuration shape across environments (different values via env vars)### Step 5: Failure Handling- Flaky test quarantine (track and isolate, don't block pipeline)- Automatic rollback on health check failure post-deploy- Notifications to PR author on failure- Pipeline run logs accessible and searchable## Checklist- [ ] All checks pass before merge allowed- [ ] Artifact built once, promoted through environments- [ ] Dependencies cached for speed- [ ] Independent stages parallelized- [ ] Deployment to staging automatic on merge- [ ] Smoke/health tests verify each deployment- [ ] Rollback mechanism defined and tested- [ ] Secrets injected at runtime, never in pipeline config- [ ] Pipeline completes in <10 minutes for feedback loop## Related Skills- `deployment/knowledge-cicd-principles` — philosophy behind the pipeline- `deployment/execution-git-workflow` — branch strategy feeding the pipeline- `infrastructure/execution-containerization` — building container artifacts

Frequently asked questions