github-actions

Review GitHub Actions workflow YAML for silent bugs and shell injection vulnerabilities.

1|Updated Jun 24, 2026
One-click install
npx skills add https://github.com/eric-sabe/engsys --skill github-actions-eric-sabe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-actions
Source: https://github.com/eric-sabe/engsys/tree/main/core/skills/github-actions
Command: npx skills add https://github.com/eric-sabe/engsys --skill github-actions-eric-sabe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of silent, hard-to-detect bugs in GitHub Actions workflows that cause CI gates to skip, fail unexpectedly, or introduce security vulnerabilities like shell injection, which can lead to broken merge pipelines and unreviewed security flaws.

Core Features & Use Cases

  • Expression Safety: Prevents silent failures from using non-existent GitHub Actions expression functions like toLower or replace, with workarounds for common string manipulation needs.
  • Secure Run Steps: Provides guidance for handling multi-line step outputs correctly and preventing shell injection from untrusted PR or event data.
  • Correct CI Trigger Configuration: Ensures draft pull request required gates run when PRs are marked ready for review, avoiding hollow green mergeable states.
  • Rate Limit Resilience: Includes patterns for handling GitHub GraphQL rate limits to prevent workflow failures during high-volume API usage. Use Case: When your team's deployment workflow is skipping required security checks for draft PRs marked ready for review, use this Skill to identify and fix the missing trigger configuration.

Quick Start

Use the github-actions skill to review your new GitHub Actions workflow for common silent bugs and security gaps before merging the pull request.

Frequently Asked Questions about github-actions

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

FAQPage Schema
How do I prevent shell injection vulnerabilities in GitHub Actions workflow run steps?

To prevent shell injection in GitHub Actions workflows, you must securely handle untrusted pull request and event data in run steps. This Skill provides guidance for correctly managing multi-line step outputs and sanitizing inputs to block security flaws.

Why do required GitHub Actions CI gates skip when draft pull requests are marked ready for review?

Required GitHub Actions CI gates skip for newly ready draft PRs due to incorrect trigger configuration. This Skill identifies and fixes the missing trigger settings to ensure required security checks run properly and avoid hollow green mergeable states.

How do I handle GitHub GraphQL rate limits to prevent workflow failures during high-volume API usage?

You handle GitHub GraphQL rate limits by implementing resilience patterns in your workflow. This Skill includes specific patterns for managing API rate limits to prevent unexpected CI failures during high-volume automated interactions.

Why do GitHub Actions expression functions like toLower or replace cause silent CI failures?

GitHub Actions expression functions like toLower or replace cause silent CI failures because they do not exist in the native expression syntax. This Skill identifies invalid functions and provides safe workarounds for common string manipulation needs.

What is the best way to review GitHub Actions workflow YAML for silent bugs before merging?

The best way to review GitHub Actions workflow YAML for silent bugs is applying an automated review Skill to catch skipped CI gates, shell injection risks, and invalid expression usage. This ensures broken merge pipelines and unreviewed security flaws are eliminated before merging.