local-ci-act

Simulate GitHub Actions workflows locally with act on macOS.

58|4|Updated Mar 8, 2026
One-click install
npx skills add https://github.com/po4yka/RIPDPI --skill local-ci-act
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: local-ci-act
Source: https://github.com/po4yka/RIPDPI/tree/main/.github/skills/local-ci-act
Command: npx skills add https://github.com/po4yka/RIPDPI --skill local-ci-act

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Local development teams often need to validate CI workflows without pushing changes or hitting CI queues. This skill provides a local testing environment for GitHub Actions using act on macOS, enabling faster feedback loops and offline parity checks.

Core Features & Use Cases

  • Local workflow simulation: run a subset or full workflow locally to verify behavior before committing.
  • Parity with CI: mirror common CI jobs to catch regressions early using the wrapper.
  • Preflight debugging: quickly test job wiring, artifacts, and matrix configurations on a developer machine.

Quick Start

Run the wrapper to simulate a workflow job locally using act.

Frequently Asked Questions about local-ci-act

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

FAQPage Schema
How do I run GitHub Actions locally on macOS without pushing changes?

Local CI testing with act simulates wrapped jobs like build, static-analysis, and e2e tests using a local wrapper. It mirrors CI parity on your macOS host to catch regressions early without cloud execution.

Do I need Docker Desktop to simulate GitHub Actions workflows with act?

Yes, Docker Desktop is required to simulate GitHub Actions workflows with act on macOS. You also need the act command-line tool and the repository's wrapper scripts and act payloads to drive deterministic local parity.

Can I test matrix configurations and job wiring for GitHub Actions before committing?

The act wrapper supports simulating a subset or full workflow locally to verify behavior before committing. You can run common jobs like rust-network-e2e and rust-native-soak to validate job wiring and configurations.

What are the limitations of using a local wrapper for GitHub Actions parity?

Limitations of local GitHub Actions parity include requiring a macOS host and specific wrapped jobs like build or static-analysis. It relies on local wrapper scripts and act payloads, meaning unsupported jobs or non-macOS environments lack deterministic parity.