skills.rest
rameshkumarchouhanr
rameshkumarchouhanrCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

ci

Monitors GitHub Actions workflows and replicates CI failures locally for triage.

Updated Aug 26, 2026
Search Tags:#automation#monitoring#github actions#test failures#triage#ci#github cli
One-click install
npx skills add https://github.com/rameshkumarchouhanr/gemni-cli --skill ci-rameshkumarchouhanr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ci
Source: https://github.com/rameshkumarchouhanr/gemni-cli/tree/main/.gemini/skills/ci
Command: npx skills add https://github.com/rameshkumarchouhanr/gemni-cli --skill ci-rameshkumarchouhanr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Waiting on CI and manually digging through GitHub Actions logs to find and reproduce failures is slow and error-prone. This Skill automates run discovery, failure triage, and local reproduction so you can fix broken builds faster. ## Core Features & Use Cases - Automatic Run Discovery: Finds the latest active or recent workflow runs for your branch using the GitHub CLI, including chained runs discovered via commit statuses—no manual run ID lookup needed. - Fail-Fast Triage: Polls every 15 seconds and stops on the first job failure, producing a noise-filtered structured failure report grouped by file or category (test, lint, build, job errors). - Local Replication: Extracts the exact npm test -w <workspace> -- <files> or npm run lint:all commands needed to reproduce failures locally. - Use Case: You push a branch and want to know immediately if CI breaks. Run the monitor, and when a test fails in packages/core, the Skill reports the failing file and hands you the exact npm test command to reproduce and verify your fix. ## Quick Start Monitor the CI status of my current branch and automatically replicate any failures locally.

Frequently Asked Questions about ci

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

FAQPage Schema
How do I monitor GitHub Actions CI status from the command line?▼

Run the ci.mjs script with your branch name: node .gemini/skills/ci/scripts/ci.mjs [branch]. It automatically discovers active runs via the GitHub CLI and polls every 15 seconds until workflows pass or a failure is detected.

How do I reproduce a GitHub Actions test failure locally?▼

When the monitor detects a failure, it outputs a structured report with a suggested command like npm test -w @google/gemini-cli-core -- <test-file>. Run that command locally to reproduce the failure and verify your fix.

Do I need to find the GitHub Actions run ID manually?▼

No. The script automatically discovers the latest active or recent runs for the branch, including chained runs found through commit statuses. You only pass a run ID when targeting a specific historical run.

What tools are required to run this CI monitoring script?▼

You need Node.js and the GitHub CLI (gh) authenticated against your repository. The script uses gh run list, gh run view, and the GitHub API to fetch job logs and statuses.

Why does the CI monitor stop before all jobs finish?▼

The monitor uses fail-fast behavior: it stops and exits with a structured failure report as soon as any job fails, rather than waiting for all workflows to complete. This surfaces actionable errors immediately.

Related Skills

Explore More Software Engineering Skills→
tile-aitile-ai
346

tilelang-github-operations

Install GitHub CLI and create pull requests via authenticated workflows.

Official
Advanced
DaFumDaFum
1

one-command-doctor

Run Node project healthchecks covering build, lint, and runtime issues.

Community
Intermediate
matteingmatteing
56

ci-preflight

Run the full CI suite locally to verify Elixir and TypeScript checks before pushing.

Community
Intermediate
fartybobofartybobo
4

resolve-ci-failures

Investigate CI/CD failures and coordinate approved fixes for GitHub Actions pipelines.

Official
Advanced