CI Replicate & Status
OfficialFreeStreamline CI failure monitoring and local replication.
Free · Opens the source repo
What CI Replicate & Status does
The CI Replicate & Status skill is designed for developers who work with GitHub Actions and want to enhance their continuous integration workflow. This skill automates the monitoring of CI workflows, allowing users to quickly identify and replicate failures locally. By simply providing the branch name, the skill takes care of run discovery and failure replication, significantly reducing the time spent on troubleshooting CI issues.
When a CI failure occurs, the skill automatically executes the necessary test or lint commands locally, enabling developers to address issues without manual intervention. This fail-fast approach ensures that the first job failure is reported immediately, allowing for a structured analysis of the problem. The skill provides real-time monitoring of all concurrent workflows on the specified branch, making it easier for developers to stay updated on the status of their CI processes.
The CI Replicate & Status skill is particularly useful for teams that rely heavily on GitHub Actions for their CI/CD pipelines. It simplifies the process of debugging by filtering out unnecessary noise from logs and focusing on the structured failure report. This means developers can quickly understand what went wrong and how to fix it, leading to a more efficient development cycle.
Overall, this skill is an essential tool for developers looking to streamline their CI workflows and improve their response to build failures. By automating failure replication and providing clear insights into CI issues, it helps teams maintain high code quality and reduces the time spent on debugging.
When to use it
Use this skill when you need to monitor GitHub Actions workflows and quickly replicate failures for debugging.
When not to use it
This skill may not be suitable if you're not using GitHub Actions or if you require more advanced CI/CD features not covered here.
What you can build with it
Quick Debugging After a CI Failure
After a CI failure is detected, use this skill to automatically replicate the failure locally and run the suggested commands for immediate triage.
Monitoring Multiple Workflows
When working with multiple workflows on a branch, this skill provides a consolidated view of their statuses, helping you manage your CI processes effectively.
Streamlining CI Troubleshooting
Use this skill to filter out noise from CI logs and focus on structured failure reports, making it easier to diagnose and fix issues.
How to install CI Replicate & Status
View source1. Install with the skills CLI
npx skills add google-gemini/gemini-cli/ci --agent claude-code2. Or install it manually
Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.
Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs
Inside SKILL.md
Written by google-geminiCI Replicate & Status
This skill enables the agent to efficiently monitor GitHub Actions, triage failures, and bridge remote CI errors to local development. It defaults to automatic replication of failures to streamline the fix cycle.
Core Capabilities
- Automatic Replication: Automatically monitors CI and immediately executes suggested test or lint commands locally upon failure.
- Real-time Monitoring: Aggregated status line for all concurrent workflows on the current branch.
- Fail-Fast Triage: Immediately stops on the first job failure to provide a structured report.
Workflow
1. CI Replicate (replicate) - DEFAULT
Use this as the primary path to monitor CI and automatically replicate failures locally for immediate triage and fixing.
- Behavior: When this workflow is triggered, the agent will monitor the CI and immediately and automatically execute all suggested test or lint commands (marked with 🚀) as soon as a failure is detected.
- Tool:
node .gemini/skills/ci/scripts/ci.mjs [branch] - Discovery: The script automatically finds the latest active or recent run for the branch. Do NOT manually search for run IDs.
- Goal: Reproduce the failure locally without manual intervention, then proceed to analyze and fix the code.
1. CI Status (status)
Use this when you have pushed changes and need to monitor the CI and reproduce any failures locally.
- Tool:
node .gemini/skills/ci/scripts/ci.mjs [branch] [run_id] - Discovery: The script automatically finds the latest active or recent run for the branch. You should NOT manually search for `run_id` using `gh run list` unless a specific historical run is requested. Simply provide the branch name.
- Step 1 (Monitor): Execute the tool with the branch name.
- Step 2 (Extract): Extract suggested `npm test` or `npm run lint` commands from the output (marked with 🚀).
- Step 3 (Reproduce): Execute those commands locally to confirm the failure.
- Behavior: It will poll every 15 seconds. If it detects a failure, it will exit with a structured report and provide the exact commands to run locally.
Failure Categories & Actions
- Test Failures: Agent should run the specific
npm test -w <pkg> -- <path>command suggested. - Lint Errors: Agent should run
npm run lint:allor the specific package lint command. - Build Errors: Agent should check
tscoutput or build logs to resolve compilation issues. - Job Errors: Investigate
gh run view --job <job_id> --logfor infrastructure or setup failures.
Noise Filtering
The underlying scripts automatically filter noise (Git logs, NPM warnings, stack trace overhead). The agent should focus on the "Structured Failure Report" provided by the tool.
Frequently asked questions about CI Replicate & Status
Similar skills
Turborepo
Optimized build system for JavaScript/TypeScript monorepos.
Azure Pipelines Validation
Streamline your Azure DevOps pipeline changes locally.
Azure Developer CLI
Streamline your Azure project workflows with best practices.
Azure Container Registry CLI
Manage Azure Container Registry resources with ease.
Aspire
Build and orchestrate polyglot distributed applications seamlessly.
Vercel CLI
Manage and deploy Vercel projects from the command line.