Act Local CI

Run GitHub Actions workflows locally with nektos/act.

Updated Jan 13, 2026
One-click install
npx skills add https://github.com/FortiumPartners/ensemble-vnext --skill act-local-ci-fortiumpartners
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Act Local CI
Source: https://github.com/FortiumPartners/ensemble-vnext/tree/main/packages/skills/act-local-ci
Command: npx skills add https://github.com/FortiumPartners/ensemble-vnext --skill act-local-ci-fortiumpartners

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill allows developers to run GitHub Actions workflows directly on their local machine, drastically reducing the feedback loop for CI/CD pipeline changes and preventing common errors before they reach the repository.

Core Features & Use Cases

  • Local Workflow Execution: Run .github/workflows/*.yml files locally.
  • Job & Event Simulation: Execute specific jobs or simulate events like push and pull_request.
  • Secret Management: Securely inject secrets and environment variables for realistic testing.
  • Use Case: A developer modifies a GitHub Actions workflow file. Before committing, they use this Skill to run the modified workflow locally, ensuring it functions as expected and doesn't break the build.

Quick Start

Run the 'test' job from your GitHub Actions workflows locally.

Frequently Asked Questions about Act Local CI

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

FAQPage Schema
How do I test GitHub Actions workflows locally before committing code?

You can test GitHub Actions workflows locally by executing .github/workflows/*.yml files directly on your machine. This approach drastically reduces the feedback loop for CI/CD pipeline changes and prevents common errors before they reach the repository.

Can I simulate specific events and jobs when running GitHub Actions locally?

Yes, local GitHub Actions execution supports job selection and event simulation. You can execute specific jobs or simulate events like push and pull_request to validate your CI/CD pipeline behavior accurately.

Do I need Docker to run GitHub Actions pipelines on my local machine?

Yes, local GitHub Actions execution integrates with Docker for runner environment simulation. Docker provides the isolated containers required to accurately replicate the CI/CD pipeline environment locally.

How do I inject secrets and environment variables for local workflow testing?

Local workflow testing supports secure secret management to inject environment variables. This allows you to perform realistic CI/CD pipeline validation by providing the necessary credentials locally before committing changes.

What is the best way to validate matrix testing in a local CI/CD environment?

Validating matrix testing in a local CI/CD environment is achieved by running GitHub Actions workflows on your machine. This supports comprehensive pipeline validation across multiple configurations before code commits.