github-actions-testing

Validate GitHub Actions workflows for cache paths and monorepo build order.

121|16|Updated Oct 10, 2025
One-click install
npx skills add https://github.com/pr-pm/prpm --skill github-actions-testing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-actions-testing
Source: https://github.com/pr-pm/prpm/tree/main/.claude/skills/github-actions-testing
Command: npx skills add https://github.com/pr-pm/prpm --skill github-actions-testing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires act, actionlint, yamllint, and includes scripts (resource) components.

What problem does it solve?

This Skill prevents GitHub Actions workflow failures by catching cache errors, path issues, monorepo dependencies, and service container problems that local testing misses.

Core Features & Use Cases

  • Pre-Push Validation: Complete workflow validation before pushing to GitHub to avoid CI failures.
  • Cache & Path Analysis: Ensure cache-dependency-path is correctly specified and all working directories exist.
  • Use Case: Imagine you're migrating to a monorepo structure. Use this Skill to validate that all workspace dependencies are built in the correct order before type checking to prevent "module not found" errors in CI.

Quick Start

Validate my GitHub Actions workflows before I push to catch cache errors and path issues.

Frequently Asked Questions about github-actions-testing

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

FAQPage Schema
How do I validate GitHub Actions workflows before pushing to catch CI failures?

Validate GitHub Actions workflows locally using actionlint for syntax errors, yamllint for YAML issues, and act to simulate job execution. This catches cache misconfigurations, path errors, and monorepo dependency problems before deployment.

What cache issues cause GitHub Actions CI failures in monorepos?

Missing or incorrect cache-dependency-path specifications prevent dependency caching from working correctly. Always specify cache-dependency-path explicitly and verify all working-directory paths exist to avoid cache misses and module-not-found errors.

Can I test GitHub Actions workflows locally without pushing to GitHub?

Yes, use act to run GitHub Actions workflows locally. Act simulates the GitHub Actions environment, letting you validate job execution, cache behavior, and service containers before committing changes.

How do I structure monorepo dependencies correctly in GitHub Actions?

Run npm ci from the repository root and ensure workspace dependencies build in the correct order before type checking. Validate this structure locally to prevent CI failures when tasks depend on unbuilt modules.

What's the best way to configure service containers in GitHub Actions workflows?

Service containers require proper configuration for networking and credential setup. Validate your service container definitions using actionlint and test them with act to ensure they work correctly in CI.