skills.rest
kiranimmadi2
kiranimmadi2COMMUNITY
Explore all skills by this author →
WebsiteGitHub

ci

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Waiting for CI results and manually digging through GitHub Actions logs to find and reproduce failures is slow and error-prone. This Skill automates run discovery, failure detection, 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 Triage: Polls every 15 seconds and stops immediately on the first job failure, producing a structured, noise-filtered 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: After pushing a branch, ask the agent to monitor CI; when a test in packages/core fails, it automatically reports the failing file and runs the matching workspace test command 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 runs for a branch?▼

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

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

The script parses failed job logs, extracts the failing test files, and prints a ready-to-run command like npm test -w @google/gemini-cli-core -- <files>. Execute that command locally to confirm the failure before fixing.

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

No. The script automatically discovers runs associated with the branch, including chained runs found through commit statuses. You only pass a run ID explicitly when targeting a specific historical run.

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

You need Node.js to execute the script and the GitHub CLI (gh) authenticated against the repository. The script derives the repo from the git remote origin URL, defaulting to google-gemini/gemini-cli.

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

It uses fail-fast triage: as soon as any job fails, it stops polling and prints a structured failure report with suggested verification commands. This avoids waiting for remaining jobs when a failure already requires attention.

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
macedotmacedot

verify

Execute lint, typecheck, and test steps via npm scripts for Node.js projects.

Community
Basic
fartybobofartybobo
4

resolve-ci-failures

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

Official
Advanced
THU-SAGETHU-SAGE
335

github

Manage GitHub issues, pull requests, and workflow runs via gh CLI.

Official
Intermediate