agent-ci

Run GitHub Actions workflows locally inside Docker for validation.

125|42|Updated May 19, 2025
One-click install
npx skills add https://github.com/SocketDev/socket-mcp --skill agent-ci-socketdev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-ci
Source: https://github.com/SocketDev/socket-mcp/tree/main/.claude/skills/fleet/agent-ci
Command: npx skills add https://github.com/SocketDev/socket-mcp --skill agent-ci-socketdev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Run GitHub Actions workflows locally inside Docker to validate changes before pushing. This enables fast feedback on workflow edits and PR updates without pushing to remote CI.

Core Features & Use Cases

  • Local CI execution of the branch workflows to catch issues early
  • Docker-based isolation that mirrors the production CI environment
  • Support for remote reusable workflows via a GitHub token and pnpm tooling
  • Quick turnaround for PRs and workflow YAML edits by validating changes locally

Quick Start

Run the local agent-ci workflow with pnpm run ci:local to validate your changes.

Frequently Asked Questions about agent-ci

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

FAQPage Schema
How do I run GitHub Actions workflows locally before pushing?

You can run GitHub Actions workflows locally in Docker to validate changes before pushing by executing the local CI environment with pnpm run ci:local. This mirrors remote runs for fast feedback on workflow edits.

Can I run GitHub Actions locally with remote reusable workflows?

Yes, running GitHub Actions locally supports workflows that reference remote reusable workflows. It requires a GitHub token for fetching them, alongside Docker and pnpm-based tooling to execute the environment.

Do I need Docker and pnpm to run GitHub Actions locally?

Yes, you need Docker and pnpm to run GitHub Actions locally. Docker provides the isolation to mirror the production CI environment, while pnpm tooling supports the execution and fetching of remote reusable workflows.

What is the best way to test GitHub Actions workflow YAML edits without triggering remote CI?

The best way to test GitHub Actions workflow YAML edits without triggering remote CI is running a local CI environment in Docker. This provides Docker-based isolation that mirrors production CI for quick turnaround on PRs.

Why does running GitHub Actions locally require a GitHub token?

Running GitHub Actions locally requires a GitHub token specifically for fetching remote reusable workflows. The token authenticates requests to pull the referenced remote workflow files during the local Docker execution.