home / skills / pluginagentmarketplace / custom-plugin-devops / cicd

cicd skill

safe

This skill helps you design and automate CI/CD pipelines across GitHub Actions, GitLab CI, and deployment strategies to speed and secure releases.

npx playbooks add skill pluginagentmarketplace/custom-plugin-devops --skill cicd

Review the files below or copy the command above to add this skill to your agents.

Files (7)

SKILL.md

2.5 KB

---
name: cicd-skill
description: CI/CD pipelines with Git, GitHub Actions, GitLab CI, Jenkins, and deployment strategies.
sasmp_version: "1.3.0"
bonded_agent: 05-cicd-automation
bond_type: PRIMARY_BOND

parameters:
  - name: platform
    type: string
    required: false
    enum: ["github-actions", "gitlab-ci", "jenkins", "argocd"]
    default: "github-actions"
  - name: operation
    type: string
    required: true
    enum: ["build", "test", "deploy", "rollback"]

retry_config:
  strategy: exponential_backoff
  initial_delay_ms: 1000
  max_retries: 3

observability:
  logging: structured
  metrics: enabled
---

# CI/CD Automation Skill

## Overview
Master CI/CD pipelines for automated software delivery.

## Parameters
| Name | Type | Required | Default | Description |
|------|------|----------|---------|-------------|
| platform | string | No | github-actions | CI/CD platform |
| operation | string | Yes | - | Pipeline operation |

## Core Topics

### MANDATORY
- Git workflows (trunk-based, GitFlow)
- Pull request best practices
- GitHub Actions workflows
- GitLab CI pipelines
- Deployment strategies

### OPTIONAL
- Jenkins pipelines
- ArgoCD GitOps
- Artifact management
- Security scanning

### ADVANCED
- Multi-environment promotion
- Feature flags
- Chaos engineering integration
- Custom actions/runners

## Quick Reference

```bash
# Git
git checkout -b feature/name
git add -p
git commit -m "type: description"
git rebase -i HEAD~3
git push -u origin feature/name

# GitHub CLI
gh pr create --title "feat: add X"
gh pr checkout 123
gh pr merge --squash
gh run list
gh run view 12345 --log

# Rollback
kubectl rollout undo deployment/app
kubectl rollout history deployment/app
```

## Deployment Strategies
| Strategy | Rollback | Use Case |
|----------|----------|----------|
| Rolling | Slow | Low-risk |
| Blue-Green | Instant | Zero-downtime |
| Canary | Fast | High-risk |

## Troubleshooting

### Common Failures
| Symptom | Root Cause | Solution |
|---------|------------|----------|
| Timeout | Slow build | Add caching |
| Test flaky | Unreliable test | Fix isolation |
| Secret missing | Not configured | Add in settings |
| Deploy failed | Auth issue | Check credentials |

### Debug Checklist
1. Check workflow syntax
2. Review full logs
3. Verify secrets set
4. Test locally if possible

### Recovery Procedures

#### Failed Deployment
1. Rollback: `kubectl rollout undo`
2. Identify issue in logs
3. Fix and redeploy

## Resources
- [GitHub Actions Docs](https://docs.github.com/actions)
- [GitLab CI Docs](https://docs.gitlab.com/ee/ci/)

Overview

This skill helps teams design, implement, and troubleshoot CI/CD pipelines across Git, GitHub Actions, GitLab CI, and Jenkins. It focuses on deployment strategies, Git workflows, and practical automation for reliable delivery. The goal is to reduce manual steps, improve deployment safety, and accelerate feedback loops.

How this skill works

The skill inspects repository structure, pipeline definitions, and common pipeline parameters to recommend improvements and fixes. It provides concrete commands, workflow templates, and rollback procedures, and explains when to apply rolling, blue-green, or canary deployments. It also surfaces troubleshooting steps for common failures like timeouts, flaky tests, and missing secrets.

When to use it

Setting up or migrating CI/CD pipelines for a new or existing repository
Standardizing Git workflows and pull request practices across teams
Implementing safe deployment strategies (rolling, blue-green, canary)
Diagnosing pipeline failures, flaky tests, and secret/config issues
Automating promotion between environments and rollback procedures

Best practices

Adopt a simple Git workflow (trunk-based or GitFlow) and enforce PR checks
Keep pipeline steps modular with caching to reduce build time
Store secrets in platform-managed secret stores, not in code
Use environment promotion and feature flags to reduce blast radius
Add clear rollback commands and validate them in runbooks

Example use cases

Create a GitHub Actions workflow that builds, tests, and deploys to staging on PR merge
Migrate Jenkins jobs to GitLab CI with pipeline-as-code and shared templates
Implement blue-green deployment for zero-downtime releases to production
Add caching and parallel test execution to cut CI time and reduce timeouts
Run a debug checklist to resolve a failing pipeline: syntax, logs, secrets, local run

FAQ

Which deployment strategy should I choose?

Choose rolling for low-risk incremental updates, blue-green for zero-downtime releases, and canary when you need staged exposure and fast rollback.

How do I recover from a failed deployment?

Run the rollback command (for Kubernetes: kubectl rollout undo), collect deployment and pipeline logs, fix the root cause, then redeploy to a validated environment.