fleet-agent-ci

Run and validate GitHub Actions workflows locally in Docker.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Run this repo's GitHub Actions workflows locally in Docker with Agent-CI to validate changes before pushing. Use before opening or updating a PR, after editing a workflow YAML under .github/workflows, or whenever catching a CI failure locally beats waiting on a remote runner.

Core Features & Use Cases

  • Local CI execution: run the repository's CI workflows locally to catch issues before pushing.
  • Deterministic debugging: reproduce and diagnose failing steps in a controlled container environment.
  • Mirror remote runners: simulate GitHub Actions workflows to validate YAML changes in PRs and forks.

Quick Start

Start a local CI run using the agent-ci toolkit by executing pnpm run ci:local to mirror your workflow runs.

Frequently Asked Questions about fleet-agent-ci

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

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

Run GitHub Actions workflows locally by using the agent-ci toolkit to execute them in Docker. This skill mirrors remote runners to validate YAML changes, letting you catch failures before pushing by executing pnpm run ci:local.

Do I need Docker to test GitHub Actions workflows in a local CI environment?

Yes, Docker is required to test GitHub Actions workflows locally. The skill uses Docker containers to create a controlled, isolated environment that mirrors remote runners for deterministic debugging of your workflow steps.

How do I debug failing GitHub Actions steps in a local container?

Debug failing GitHub Actions steps locally by reproducing the CI run in an isolated Docker container. The skill surfaces a JSON event stream alongside human-readable logs, allowing you to diagnose workflow failures deterministically before updating a PR.

Can I validate workflow YAML changes for PRs and forks using local CI?

Yes, you can validate workflow YAML changes for PRs and forks using local CI. The skill simulates GitHub Actions workflows locally in Docker, ensuring your YAML modifications work correctly before committing them to a remote branch or pull request.

What is the best way to mirror remote runners for GitHub Actions locally?

The best way to mirror remote runners locally is using the agent-ci tool within Docker. This skill provides a controlled container environment that accurately simulates GitHub Actions workflows, enabling fast and isolated CI tests for your repository.

Why wait for remote runners when you can catch CI failures locally?

Waiting for remote runners wastes time; catching CI failures locally speeds up development. By running workflows in Docker with agent-ci, you get immediate feedback and deterministic debugging through JSON event streams and readable logs before pushing.