Automate CI/CD and Development Workflows

This is a workflow-automation skill for designing CI/CD pipelines, GitHub Actions workflows, and automated development processes that reduce manual work and improve consistency while maintaining quality and security. Its workflow: 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; and document the rollout, rollback, and notification strategy. Output follows a fixed format: a summary of pipeline stages and triggers, proposed workflow files or a step list, required secrets/env vars/service integrations, and risks, assumptions, and rollback notes. It carries an explicit safety constraint: never run deployment steps without approvals and a rollback plan, and treat secrets and environment-configuration changes as high risk.

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/deployment steps, or improving pipeline reliability, visibility, or compliance checks. Don't use it for a one-off command or quick troubleshooting, when there's no workflow or automation context, or for a task that's strictly product or UI design. Detailed workflow patterns are available in a companion resources/implementation-playbook.md file.

Input is the current build, test, and deploy steps plus target environments; output is a proposed pipeline - stages, caching, quality gates, security scans, required secrets and integrations - plus a documented rollback and notification strategy.

Engineering and platform teams automating CI/CD pipelines who need consistent stage design, security scanning, and rollback planning built in, rather than assembling pipelines ad hoc.