fleet-greening-ci-local

Run GitHub Actions workflows locally in Docker and retry failed steps until green.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Drive a repo's CI to green LOCALLY with Agent-CI (Docker), the local analog of greening-ci. Runs a workflow (or all PR/push workflows) in containers, and on the first paused step reads the failure log, fixes the code locally, and agent-ci retries the SAME paused runner — looping until the run lands green or a wall-clock budget expires. Use to validate a workflow change or a release dispatch BEFORE burning a remote run, to catch a CI failure on your own machine, or as the local pre-flight before republishing-stubs / any remote build-matrix dispatch. Where greening-ci watches GitHub Actions remotely and fixes-then-pushes, this runs in local containers and fixes-then-retries in place — no push, no remote runner minutes.

Core Features & Use Cases

  • Local Docker-based execution of CI workflows via Agent-CI to validate changes without remote runners.
  • Read failure logs of paused steps, apply fixes locally, and retry the SAME runner until green or budget expiry.
  • Use Case: Validate a workflow change or deployment before remote dispatch to avoid wasted minutes on remote runners.

Quick Start

Run the local Agent-CI workflow to reproduce a paused step, fix the failing code, and retry the same runner until the workflow completes green or the budget expires.

Frequently Asked Questions about fleet-greening-ci-local

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

FAQPage Schema
How do I run GitHub Actions workflows locally in Docker to validate changes before pushing?

Local CI validation in Docker reproduces paused workflow steps, reads failure logs, applies local code fixes, and retries the same runner in a loop until workflows land green or a wall-clock budget expires.

What is the best way to debug CI failures locally without burning remote runner minutes?

Local containerized CI execution with Agent-CI catches failures on your own machine by fixing and retrying paused steps in place, avoiding remote runner minutes and remote pushes entirely.

How do I automatically fix and retry failing CI steps in a loop?

Agent-CI loops fix-and-retry cycles by reading the failure log of the first paused step, applying local code fixes, and retrying the same paused runner until green or wall-clock budget expiry.

Does local CI validation in Docker require pushing code to trigger a remote run?

No, local containerized CI validation fixes and retries in place without pushing code or triggering remote runs, serving as a local preflight check before remote dispatch or republishing stubs.

What happens if my local CI workflow does not reach green status before the time limit?

The fix-and-retry loop terminates when the wall-clock budget expires, halting automated retries and leaving the paused workflow state and failure logs available for manual inspection.