github-actions

Review GitHub Actions workflows for syntax, permissions, and security.

20|4|Updated May 14, 2026
One-click install
npx skills add https://github.com/crewrig/crewrig --skill github-actions-crewrig
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-actions
Source: https://github.com/crewrig/crewrig/tree/main/artifacts/core/skills/github-actions
Command: npx skills add https://github.com/crewrig/crewrig --skill github-actions-crewrig

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps you author, review, debug, and harden GitHub Actions workflows without relying on guesswork. It turns CI/CD configuration into a disciplined, security-aware practice so pipelines are reproducible, least-privilege, and easier to maintain.

Core Features & Use Cases

  • Workflow authoring and review: Create or audit .github/workflows/ files with correct syntax, clean job structure, and reliable triggers.
  • Security hardening: Apply safe defaults for permissions, secret handling, OIDC federation, action pinning, and untrusted-input handling.
  • Debugging and optimization: Diagnose failures in runners, caching, expressions, reusable workflows, and matrix builds.
  • Use case: A pull request changes a deployment pipeline; this Skill guides the review, flags unsafe permissions or unpinned actions, and recommends a secure fix.

Quick Start

Ask the assistant to review my GitHub Actions workflow for correctness, security, and best-practice improvements.

Frequently Asked Questions about github-actions

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

FAQPage Schema
How do I secure GitHub Actions workflows with least-privilege permissions and OIDC?

Securing GitHub Actions workflows requires applying strict least-privilege permissions, configuring OIDC federation for cloud access, and pinning action references to safe immutable versions. This approach prevents unauthorized access and ensures reproducible, hardened CI/CD pipelines.

What is the best way to debug caching and runner failures in GitHub Actions?

Debugging GitHub Actions runner and caching failures involves validating safe expression handling, diagnosing matrix builds, and reviewing documented runner behavior. Analyzing these components ensures reliable workflow execution and resolves pipeline execution failures effectively.

How do I create reusable workflows and composite actions for GitHub Actions?

Creating reusable GitHub Actions workflows requires defining clean job structures, correct syntax, and reliable triggers for workflow_call pipelines. Using strict permission boundaries and pinned references ensures secure, maintainable, and reproducible composite action design.

How do I review GitHub Actions pull requests for unsafe secrets and unpinned actions?

Reviewing GitHub Actions pull requests involves checking for unsafe permissions, unpinned action references, and improper untrusted-input handling. Applying disciplined security hardening validates the workflow syntax and flags vulnerable secret configurations for immediate remediation.

Does this GitHub Actions review process work with matrix builds and workflow_call pipelines?

Yes, the GitHub Actions review process handles matrix builds and workflow_call pipelines by diagnosing failures, validating safe expression handling, and ensuring least-privilege permissions. It applies to authoring, debugging, and hardening complex reusable workflow configurations.