skills.rest
dxiiren
dxiirenCOMMUNITY
Explore all skills by this author →
GitHub

monitor-ci

Watches GitHub Actions CI runs for the current branch and surfaces failing job logs.

Updated Aug 1, 2026
Search Tags:#workflow#monitoring#pull request#github actions#gh cli#build status#ci
One-click install
npx skills add https://github.com/dxiiren/project-skeleton --skill monitor-ci-dxiiren
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: monitor-ci
Source: https://github.com/dxiiren/project-skeleton/tree/main/.claude/skills-optional/monitor-ci
Command: npx skills add https://github.com/dxiiren/project-skeleton --skill monitor-ci-dxiiren

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After pushing a commit or opening a PR, developers often need to know whether the CI pipeline passed without manually refreshing the GitHub Actions page or digging through logs when something fails. ## Core Features & Use Cases - Run Discovery: Finds the latest GitHub Actions run for the current branch or PR using the gh CLI. - Live Watching: Streams the run to completion with gh run watch, exiting non-zero on failure as a pass/fail signal. - Failure Diagnosis: Pulls the failing job's log with --log-failed and reports the root-cause error lines plus a suggested next step. - Use Case: After pushing a commit, ask the assistant to watch the CI run; when it finishes you get a per-job pass/fail summary and, on failure, the exact error lines from the offending job. ## Quick Start Ask the assistant to monitor the CI run for the current branch and report which jobs passed or failed.

Frequently Asked Questions about monitor-ci

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

FAQPage Schema
How do I watch a GitHub Actions run from the command line?▼

Use gh run watch <run-id> --exit-status to stream a run's progress until it reaches a terminal state. The command exits non-zero if the run fails, giving you a direct pass/fail signal without polling the web UI.

How do I find the CI run for my current branch?▼

Run gh run list --branch "$(git branch --show-current)" --limit 5 to see recent runs with their IDs and statuses. Pick the newest run ID for the CI workflow triggered by your latest push or PR.

How do I see only the failed steps in a GitHub Actions log?▼

Use gh run view <run-id> --log-failed to print only the failed steps' logs. For a specific job's full output, use gh run view <run-id> --job <job-id> --log.

What if the gh CLI is not authenticated?▼

Check authentication with gh auth status; if it fails, run gh auth login first. As a fallback, the GitHub MCP Actions tools can be used instead of the gh CLI.

Can I check PR status without watching the full run?▼

Yes, gh pr checks <pr-number> gives a compact pass/fail summary of all checks on a pull request. This is faster than watching the run when you only need the overall status.

Related Skills

Explore More Software Engineering Skills→
tribedotruntribedotrun
8

mando-pr

Create GitHub pull requests and trigger AI reviewers with CI monitoring.

Official
Advanced
Cohey0727Cohey0727

resolve-ci

Diagnose and fix failing CI checks on GitHub pull requests using gh CLI.

Community
Advanced
matteingmatteing
56

ci-preflight

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

Community
Intermediate
kotahashihamakotahashihama

wait-ci

Waits for GitHub Actions workflow runs to complete in the background using run ID comparison.

Community
Intermediate