CI/CD Pipeline

**Overall judgment:** High-quality, focused skill for GitHub Actions CI/CD. It provides well-structured, modern examples and covers the full lifecycle from basic CI to multi-environment deployments, Docker, and release automation. Best suited for users who are specifically on GitHub and want practical, production-leaning workflows. **Strengths** - Rich library of ready-to-adapt workflow templates for common stacks (Node, Python, Go, Rust). - Covers advanced patterns: matrix builds, concurrency controls, path filters, monorepo workflows, reusable workflows, and caching. - Good operational guidance: secrets via `gh` CLI, environment protection rules, debugging with `gh run` and `tmate`, validation with actionlint. - Examples use current major action versions and idiomatic GitHub Actions features. **Key risks / limitations** - **Platform-specific**: Essentially only useful for GitHub Actions; patterns don’t directly transfer to GitLab CI, CircleCI, etc. - **Production safety still depends on the user**: While it shows environment protection and secrets management, misconfiguration (e.g., overly permissive permissions, deploy-on-every-push) is still possible if the user simplifies examples incorrectly. - **Security hardening is hinted but not fully enforced**: It advises pinning actions to SHAs for supply-chain security but examples mostly pin to major tags. **Recommended scenarios** - You need to add CI/CD to a GitHub repo from scratch or modernize an existing, ad-hoc workflow. - You want to implement reliable testing and linting pipelines for Node/Python/Go/Rust with minimal trial-and-error. - You’re building automated release pipelines (tag-based releases, GitHub Releases, npm publish, Docker images to GHCR). - You’re troubleshooting flaky or failing GitHub Actions workflows and need concrete debugging and optimization patterns. **Avoid / use cautiously** - If your CI/CD runs on non-GitHub providers (GitLab, Jenkins, etc.), this skill won’t be directly applicable. - In highly regulated environments, additional review is needed for permissions, secrets policies, and action pinning beyond the generic examples provided.

**Quick judgement**: Strong, focused skill for CI/CD on **GitHub Actions**. It provides well-structured examples and patterns for common languages and deployment scenarios, with solid coverage of caching, matrix builds, secrets, and debugging. It is best when the user explicitly wants GitHub Actions, and less suitable if they need other CI providers or very specialized enterprise patterns. **Strengths and coverage** - Good practical breadth: basic CI for Node/Python/Go/Rust, deployment on branches/tags, Docker image build/push, npm publish on release. - Modern patterns: matrix strategy, concurrency groups, path filters, monorepo selective testing, reusable workflows, environment protection, artifact handling. - Operational guidance: how to inspect and re-run workflows with `gh` CLI, use `actionlint`, debug failures, and attach tmate for SSH debugging. - Security-awareness: use of secrets via `secrets.*`, environment-specific secrets, permission blocks, and advice to pin actions to SHAs. **Risks / limitations** - **GitHub Actions–only**: not appropriate when users are on GitLab CI, CircleCI, Jenkins, or other platforms. - **Security depth**: good baseline practices but not a full treatment of supply-chain, OIDC to cloud providers, or complex secret-rotation/compliance scenarios. - **Domain breadth**: strong for typical app CI/CD, but less coverage for highly specialized workflows (e.g., complex infra-as-code pipelines, mobile build pipelines, or multi-repo orchestration). **Recommended scenarios** - Users on GitHub who need: (1) first-time CI setup, (2) deployment pipelines (staging/production), or (3) automated release and publishing flows. - Teams debugging flaky or failing GitHub Actions workflows and wanting concrete patterns to fix caching, permissions, triggers, or job duplication. - Projects wanting to optimize CI performance using matrix builds, caching, concurrency control, and monorepo-aware workflows.