cicd-pipeline

Engineer CI/CD pipelines with deterministic caching and SHA-tagged immutable deployments.

8|1|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/drewid74/ai_skills --skill cicd-pipeline-drewid74
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cicd-pipeline
Source: https://github.com/drewid74/ai_skills/tree/main/cicd-pipeline
Command: npx skills add https://github.com/drewid74/ai_skills --skill cicd-pipeline-drewid74

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you engineer a CI/CD pipeline that stops failing unpredictably, speeds up builds, and produces reproducible deploy artifacts across environments.

Core Features & Use Cases

  • Platform and runner setup: Choose GitHub Actions for GitHub-hosted repos or Forgejo Actions for self-hosted git, and place runners safely for private network needs.
  • Deterministic caching and build performance: Use dependency lock hashing and Docker BuildKit cache strategies to reduce cache misses and cold starts.
  • Safe, immutable releases: Promote the same image built from a commit SHA through staging and production, with OIDC-ready permissions and semantic-release automation.
  • Operational guardrails: Add concurrency cancellation, scoped job permissions, security scanning before push, and quality checks that catch regressions early.
  • Use Case: If your PR builds are flaky and every run rebuilds dependencies, use this Skill to parallelize jobs, stabilize caching, and ensure each deployment is tied to a specific commit SHA.

Quick Start

Ask the AI to design your CI/CD workflow for a failing or slow pipeline on GitHub Actions (including OIDC permissions, caching, parallel jobs, image build+push, and staged promotion by commit SHA).

Frequently Asked Questions about cicd-pipeline

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix flaky GitHub Actions workflows and slow builds with cache misses?

To fix flaky GitHub Actions workflows, you can parallelize jobs, apply deterministic dependency lock hashing, and use Docker BuildKit cache strategies to eliminate cache misses and reduce cold starts.

How do I set up immutable deploys with commit SHA-tagged image promotion?

Immutable deploys are set up by building a Docker image tagged with a specific commit SHA and promoting that exact image through staging and production, ensuring reproducible artifacts across environments.

Can I use self-hosted runners with Forgejo Actions for private network CI/CD?

Yes, you can use Forgejo Actions for self-hosted git repositories and safely place runners to handle private network needs, applying the same caching and immutable release strategies as GitHub Actions.

What's the best way to secure automated release pipelines with OIDC and scoped permissions?

The best way to secure automated release pipelines is by applying OIDC-ready permissions, pinning action versions, enforcing scoped job permissions, and running pre-push vulnerability scanning before deployment.

Why do my CI/CD pipelines rebuild dependencies every time and how do I stop it?

CI/CD pipelines rebuild dependencies due to non-deterministic caching keys; you stop this by implementing deterministic dependency lock hashing alongside Docker BuildKit cache strategies to persist cache across runs.

Do I need concurrency cancellation controls for parallel job execution in GitHub Actions?

Yes, concurrency cancellation controls are needed to cancel outdated parallel jobs, preventing conflicting deployments and ensuring only the latest commit SHA progresses through the pipeline.