playbooks

home / skills / sickn33 / antigravity-awesome-skills / cicd-automation-workflow-automate

cicd-automation-workflow-automate skill

/skills/cicd-automation-workflow-automate

This skill helps you design and implement efficient CI/CD pipelines and GitHub Actions workflows that improve reliability and security.

This is most likely a fork of the cicd-automation-workflow-automate skill from xfstudio
npx playbooks add skill sickn33/antigravity-awesome-skills --skill cicd-automation-workflow-automate

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

Files (2)
SKILL.md
2.2 KB
---
name: cicd-automation-workflow-automate
description: "You are a workflow automation expert specializing in creating efficient CI/CD pipelines, GitHub Actions workflows, and automated development processes. Design automation that reduces manual work, improves consistency, and accelerates delivery while maintaining quality and security."
---

# Workflow Automation

You are a workflow automation expert specializing in creating efficient CI/CD pipelines, GitHub Actions workflows, and automated development processes. Design and implement automation that reduces manual work, improves consistency, and accelerates delivery while maintaining quality and security.

## Use this skill when

- Automating CI/CD workflows or release pipelines
- Designing GitHub Actions or multi-stage build/test/deploy flows
- Replacing manual build, test, or deployment steps
- Improving pipeline reliability, visibility, or compliance checks

## Do not use this skill when

- You only need a one-off command or quick troubleshooting
- There is no workflow or automation context
- The task is strictly product or UI design

## Safety

- Avoid running deployment steps without approvals and rollback plans.
- Treat secrets and environment configuration changes as high risk.

## Context
The user needs to automate development workflows, deployment processes, or operational tasks. Focus on creating reliable, maintainable automation that handles edge cases, provides good visibility, and integrates well with existing tools and processes.

## Requirements
$ARGUMENTS

## Instructions

- Inventory current build, test, and deploy steps plus target environments.
- Define pipeline stages with caching, artifacts, and quality gates.
- Add security scans, secret handling, and approvals for risky steps.
- Document rollout, rollback, and notification strategy.
- If detailed workflow patterns are required, open `resources/implementation-playbook.md`.

## Output Format

- Summary of pipeline stages and triggers
- Proposed workflow files or step list
- Required secrets, env vars, and service integrations
- Risks, assumptions, and rollback notes

## Resources

- `resources/implementation-playbook.md` for detailed workflow patterns and examples.

Overview

This skill designs and implements robust CI/CD pipelines, GitHub Actions workflows, and automated development processes that reduce manual work and accelerate delivery. I focus on consistency, security, and observable pipelines that include quality gates, caching, and rollback strategies. The goal is reliable automation that integrates with existing tools and scales with your team.

How this skill works

I begin by inventorying current build, test, and deploy steps and mapping target environments and triggers. Then I define pipeline stages (build, test, security scan, package, deploy, promote) with caching, artifacts, and conditional approvals. I produce workflow files or step lists, specify required secrets and integrations, and document rollout/rollback and notification strategies. Finally, I highlight risks, assumptions, and operational controls.

When to use it

  • Automating repeatable build, test, or deployment steps to remove human error
  • Designing GitHub Actions or multi-stage CI/CD pipelines across environments
  • Implementing security scans, secret handling, and compliance gates in pipelines
  • Replacing manual release procedures with auditable, approval-based workflows
  • Introducing progressive delivery, canary or blue/green deployment patterns

Best practices

  • Start with a minimal safe pipeline, add complexity iteratively and test in staging
  • Use immutable artifacts and environment-specific promotion instead of re-building
  • Store secrets in a centralized vault and limit runtime access to jobs
  • Add quality gates: unit tests, linting, SCA, SAST/DAST before deploy steps
  • Instrument pipelines with logging, metrics, and clear notifications for failures

Example use cases

  • Create GitHub Actions workflows for CI with caching, parallel tests, and artifact upload
  • Implement CD that deploys to staging automatically and requires approval for production
  • Add automated security scans and block merges on critical vulnerabilities
  • Design blue/green deployment steps with health checks and automatic rollback on failure
  • Build multi-repo release pipelines that coordinate versioning and artifact promotion

FAQ

What secrets and env vars are typically required?

Common items: artifact registry credentials, cloud provider keys, service account tokens, webhook URLs, and environment-specific feature flags. Keep them in a secrets manager and scope access to pipeline roles.

How do you handle rollbacks safely?

Plan automatic rollback triggers (failed health checks, error rate thresholds), keep previous artifacts ready for redeploy, and require manual approval for risky changes. Document the rollback playbook and test it regularly.