skills.rest
bkrsna
bkrsnaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

ci

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

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

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 a branch using the GitHub CLI, including chained runs discovered via commit statuses—no manual run ID lookup needed. - Fail-Fast Structured Reports: Polls jobs every 15 seconds and stops on the first failure, emitting a noise-filtered report that categorizes issues as test, lint, build, or job errors. - Local Failure Replication: Extracts the exact npm test -w <workspace> -- <file> or npm run lint:all commands needed to reproduce failures locally. - Use Case: After pushing a branch, ask the agent to monitor CI; when a test in packages/core fails, the Skill reports the failing file and immediately runs the matching workspace test command locally so you can verify the fix. ## Quick Start Ask the agent to monitor CI on the 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 a branch name and it uses the GitHub CLI to find active runs, then polls job status every 15 seconds. It prints a live status line and exits with a structured report when failures are detected.

How to reproduce a GitHub Actions test failure locally?▼

The script parses failed job logs, extracts the failing test file paths, and maps them to npm workspaces. It then outputs a ready-to-run command like npm test -w @google/gemini-cli-core -- <file> so you can confirm the failure locally.

Do I need to find the workflow run ID manually?▼

No. The script automatically discovers the latest active or recent runs for the branch via gh run list and commit status APIs, including chained workflows. You only pass a run ID when targeting a specific historical run.

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

You need Node.js, git, and the GitHub CLI (gh) authenticated to the repository. The script shells out to gh for run and job data and to git for branch and remote detection.

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

It uses a fail-fast strategy: as soon as any job reports a failure, it stops polling and prints a noise-filtered failure report with reproduction commands. This prioritizes quick feedback over waiting for the full suite.

Related Skills

Explore More Software Engineering Skills→
Renzo-TognellaRenzo-Tognella

yeet

Automate GitHub pull request creation using the GitHub CLI.

Community
Intermediate
SynkraAISynkraAI
3.1k

aiox-quality-gates

Runs lint, typecheck, test, and pre-push quality gates for AIOX projects.

Official
Basic
ArthTech-AIArthTech-AI

precheck

Run local pre-push tests on changed hooks, skills, and manifests.

Official
Advanced
benzwickbenzwick

download-ci-artifacts

Download GitHub Actions CI artifacts using gh CLI commands.

Community
Intermediate