github-actions-validator

Validate GitHub Actions workflow files with static analysis and local execution checks.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/ToanPV90/dotfiles --skill github-actions-validator-toanpv90
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-actions-validator
Source: https://github.com/ToanPV90/dotfiles/tree/main/claude/.claude/skills/github-actions-validator
Command: npx skills add https://github.com/ToanPV90/dotfiles --skill github-actions-validator-toanpv90

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

It helps you validate, lint, and debug GitHub Actions workflow files before merging by catching syntax issues, runner label mistakes, expression problems, security risks, and outdated action versions early.

Core Features & Use Cases

  • Validate workflows end-to-end by running actionlint-style static checks and optional local execution via act.
  • Security and correctness guardrails including error-to-reference mapping and detection of risky patterns like script injection and insecure usage.
  • Action version verification against a maintained list, with offline “UNVERIFIED” handling for unknown versions.

Quick Start

Run the validator on a single workflow file: bash "$SKILL_DIR/scripts/validate_workflow.sh" .github/workflows/ci.yml

Frequently Asked Questions about github-actions-validator

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

FAQPage Schema
How do I validate GitHub Actions workflow files before pushing to CI?

GitHub Actions workflow validation catches syntax issues, runner label mistakes, and expression problems before CI by running static analysis and local execution checks on .github/workflows/*.yml files to prevent build failures.

What does actionlint check for in GitHub Actions workflows?

Actionlint checks GitHub Actions workflows for syntax errors, invalid runner labels, expression problems, and insecure patterns like script injection, mapping each error to reference sections for precise workflow remediation.

How do I test GitHub Actions workflows locally without triggering CI?

Local testing of GitHub Actions workflows uses act for execution simulation and actionlint for static linting, validating workflow behavior and detecting security risks locally without triggering remote CI runs.

Can I check for outdated action versions in my GitHub workflows?

Action version verification checks GitHub workflow references against a maintained list, flagging outdated versions for updates and assigning UNVERIFIED status to unknown versions for offline handling and security auditing.

Why is my GitHub Actions workflow failing security checks?

GitHub Actions workflows fail security audits when static analysis detects risky patterns like script injection or insecure usage, triggering error mapping to reference sections and minimal-quote fixes followed by mandatory post-fix reruns.

What are the limitations of local GitHub Actions workflow testing?

Local GitHub Actions testing cannot fully replicate remote CI environments and returns UNVERIFIED status for action versions not on the maintained list, requiring manual review of unmapped errors and offline reference section handling.