act-local-ci

Execute and debug GitHub Actions workflows locally with the act CLI tool.

57|7|Updated Aug 6, 2025
One-click install
npx skills add https://github.com/seiggy/lucia-dotnet --skill act-local-ci
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: act-local-ci
Source: https://github.com/seiggy/lucia-dotnet/tree/main/.github/skills/act-local-ci
Command: npx skills add https://github.com/seiggy/lucia-dotnet --skill act-local-ci

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill allows you to run and debug GitHub Actions workflows directly on your local machine, eliminating the need to push code to a remote repository for every test.

Core Features & Use Cases

  • Local Workflow Execution: Simulate GitHub Actions runners and execute workflows in Docker containers.
  • Debugging CI/CD: Troubleshoot pipeline failures without committing or pushing changes.
  • Event Simulation: Test workflows triggered by various GitHub events like push, pull_request, and workflow_dispatch.
  • Secrets & Variables Management: Securely handle secrets and variables for local runs.

Quick Start

Use the act-local-ci skill to run the default push event for all workflows in your repository.

Frequently Asked Questions about act-local-ci

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

FAQPage Schema
How do I run GitHub Actions workflows locally without pushing to a remote repository?

Run GitHub Actions workflows locally using the act CLI tool to simulate runners and execute jobs in Docker containers. This allows you to validate workflow file changes and test CI/CD pipelines directly on your machine without committing or pushing code.

Can I simulate specific GitHub events like pull_request or workflow_dispatch for local workflow debugging?

Yes, you can simulate specific GitHub events for local workflow debugging using the act CLI. The tool supports event simulation for triggers like push, pull_request, and workflow_dispatch to test how your workflows respond to various GitHub events.

How do I handle GitHub Actions secrets and variables when testing workflows on my local machine?

Handle GitHub Actions secrets and variables during local testing by configuring them securely for your act CLI runs. The tool supports secrets and variables management, allowing you to safely pass sensitive data into your local workflow executions.

Do I need Docker to execute and debug CI/CD pipelines with the act CLI?

Yes, Docker is required to execute and debug CI/CD pipelines with the act CLI because it simulates GitHub Actions runners within Docker containers. This containerized environment provides the necessary isolation and runner image selection for accurate local testing.

What is the best way to troubleshoot failing GitHub Actions jobs before committing changes?

The best way to troubleshoot failing GitHub Actions jobs before committing changes is to use the act CLI for local execution. It facilitates job targeting and workflow debugging, enabling you to identify and fix CI/CD pipeline failures without pushing to GitHub.

Why are my GitHub Actions workflows not working when tested locally with act?

GitHub Actions workflows may not work when tested locally with act due to incorrect runner image selection, missing secrets and variables, or unsupported event simulation. Use the act CLI's job targeting feature to isolate and debug specific workflow failures.