Skip to content
Back to skills

Ci Cd

ASecurity

Workflow for creating a complete CI/CD pipeline. Use when the user needs to set up or modify CI/CD pipelines.

  • 30 stars
  • 0 votes
  • 0 copies
  • 4 views
  • Added May 27, 2026
developmenttestinggitci/cdsecurity

Security analysis

A100/100

Scanned May 27, 2026

npx -y skills add girijashankarj/cursor-handbook --skill ci-cd --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Ci Cd?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Ci Cd
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/girijashankarj-ci-cd/badge)](https://www.skillsdirectory.com/skills/girijashankarj-ci-cd)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: ci-cd
description: Workflow for creating a complete CI/CD pipeline. Use when the user needs to set up or modify CI/CD pipelines.
---

# Skill: Set Up CI/CD Pipeline

## Trigger
When the user needs to set up or modify CI/CD pipelines.

## Steps

### Step 1: Define Pipeline Stages
- [ ] Lint and format check
- [ ] Type check: `{{CONFIG.testing.typeCheckCommand}}`
- [ ] Unit tests: `{{CONFIG.testing.testCommand}}`
- [ ] Build
- [ ] Integration tests
- [ ] Security scan
- [ ] Deploy

### Step 2: Create Pipeline Configuration
- [ ] Create workflow file (`.github/workflows/ci.yml` for GitHub Actions)
- [ ] Define trigger events (push, PR, schedule)
- [ ] Configure job runners and environments
- [ ] Set up caching for dependencies

### Step 3: Configure Secrets
- [ ] List required secrets
- [ ] Add to CI/CD secrets store (never in code)
- [ ] Document required secrets in README

### Step 4: Add Quality Gates
- [ ] Tests must pass (0 failures)
- [ ] Coverage ≥ {{CONFIG.testing.coverageMinimum}}%
- [ ] No type errors
- [ ] No critical security vulnerabilities
- [ ] Build succeeds

### Step 5: Set Up Deployment
- [ ] Configure environment promotion (dev → staging → prod)
- [ ] Add manual approval for production
- [ ] Configure rollback triggers
- [ ] Set up smoke tests post-deployment

### Step 6: Test Pipeline
- [ ] Trigger on a test branch
- [ ] Verify all stages complete
- [ ] Verify failure handling (intentionally break a stage)
- [ ] Verify notifications work

## If a step fails

| Step | Failure | Recovery |
|------|---------|----------|
| Step 4 | Quality gate blocks pipeline | Fix failing tests, coverage, or type errors locally; do not lower thresholds to pass |
| Step 5 | Deploy stage fails | Check secrets and env vars; verify target environment is reachable; rollback if prod deploy partially applied |
| Step 6 | Pipeline fails on test trigger | Fix the broken stage; verify failure handling works (pipeline should fail fast, not deploy on failure) |

Never remove manual approval for production. Never deploy on failure.

## Completion
CI/CD pipeline is running, tested, and documented.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…