github-actions-cicd

Create, audit, and troubleshoot GitHub Actions CI/CD workflows with security and deployment checklists.

Updated Jun 13, 2026
One-click install
npx skills add https://github.com/jenreh/project-kit-template --skill github-actions-cicd-jenreh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-actions-cicd
Source: https://github.com/jenreh/project-kit-template/tree/main/.agents/agent-skills/skills/github-actions-cicd
Command: npx skills add https://github.com/jenreh/project-kit-template --skill github-actions-cicd-jenreh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Building and maintaining GitHub Actions pipelines involves many failure points: misconfigured triggers, over-privileged permissions, broken caches, missing approval gates, and hard-to-debug flaky runs. This Skill provides structured modes for creating new workflows, auditing existing ones, and diagnosing common failures. ## Core Features & Use Cases - Workflow Creation: Scaffolds CI/CD pipelines with least-privilege permissions, concurrency control, caching, pinned action versions, and OIDC-based cloud authentication. - Security & Performance Audits: Runs a structured checklist covering secrets handling, dependency review, SAST integration, cache key design, and matrix parallelism. - Troubleshooting Guides: Diagnoses non-triggering workflows, 403 permission errors, cache misses, flaky tests, and slow pipelines with step-by-step fixes. - Use Case: A team needs to deploy to AWS from GitHub without long-lived credentials. Use this Skill to configure OIDC with aws-actions/configure-aws-credentials, add a production environment with manual approval, and enforce dependency review on pull requests. ## Quick Start Ask the assistant to create a GitHub Actions workflow that runs tests on pull requests and deploys to production with OIDC authentication and a manual approval gate.

Frequently Asked Questions about github-actions-cicd

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

FAQPage Schema
How do I create a GitHub Actions CI/CD workflow?

Define trigger events like push or pull_request, add a concurrency group to cancel redundant runs, set least-privilege permissions, and structure jobs for lint, test, build, and deploy. Pin all actions to major version tags and configure caching keyed on your lockfile.

How to set up OIDC authentication for AWS in GitHub Actions?

Grant id-token: write permission in the workflow, then use aws-actions/configure-aws-credentials@v4 with the role ARN and region. This replaces long-lived access keys with short-lived tokens, requiring a matching trust policy in AWS IAM.

Why is my GitHub Actions workflow not triggering?

Check that the on: trigger matches the actual event and that branches or paths filters are not too narrow. Also verify the concurrency group is not blocked by a prior run and that branch protection rules are not preventing execution.

Why does my GitHub Actions cache miss on every run?

Cache misses happen when the key does not match the lockfile hash or the path does not match where the package manager installs dependencies. Print the computed key in a run step and verify the hashFiles pattern, using ** for monorepo layouts.

How do I add a manual approval gate before production deployment?

Use an environment block with the name production in the deploy job and configure protection rules requiring reviewer approval in repository settings. Chain it with needs: deploy-staging so production only runs after staging succeeds.

What security checks should a GitHub Actions pipeline include?

Pin actions to commit SHAs or major version tags, scope permissions explicitly, use OIDC instead of static cloud keys, run dependency-review-action on pull requests, and integrate a SAST tool like CodeQL or Bandit that blocks on critical findings.