ci-status

Show GitHub Actions workflow run statuses and failing steps for the current branch.

1|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/jrmatherly/shipit --skill ci-status-jrmatherly
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ci-status
Source: https://github.com/jrmatherly/shipit/tree/main/.claude/skills/ci-status
Command: npx skills add https://github.com/jrmatherly/shipit --skill ci-status-jrmatherly

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a concise CI/CD status summary for the current git branch, surfacing job-level results and failing steps so engineers can quickly identify what broke without manually inspecting multiple workflow runs.

Core Features & Use Cases

  • Branch-focused visibility: Lists recent workflow runs for the current branch and summarizes run name, status, and conclusion.
  • Job and step diagnostics: Shows job-level statuses and extracts failing steps to pinpoint root causes of CI failures.
  • Live watch and verification: Offers the option to watch in-progress runs and recommends re-checking run lists after watching completes.
  • Use Case: When a feature branch triggers multiple workflows after a push, use this Skill to find which run and which job failed and which specific step caused the failure before creating fixes or updating a PR.

Quick Start

Run the ci-status skill to list recent workflow runs for the current branch, display job-level pass/fail status and failing steps, and optionally watch in-progress runs.

Frequently Asked Questions about ci-status

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

FAQPage Schema
How do I check GitHub Actions workflow status for a specific git branch?

You can check GitHub Actions workflow status by listing recent workflow runs for the current branch using gh run list. This Skill summarizes run names, statuses, and conclusions, providing a concise CI/CD pipeline overview without manually inspecting each run.

How do I find which specific job and step caused a GitHub Actions failure?

Finding which specific job and step caused a GitHub Actions failure involves using gh run view to inspect job-level statuses. This Skill extracts failing steps from workflow runs, pinpointing the exact root cause of CI failures on your branch.

Can I watch in-progress GitHub Actions workflow runs from the command line?

Yes, you can watch in-progress GitHub Actions workflow runs from the command line using gh run watch. This Skill offers the option to monitor live run progress and recommends re-checking the run list after watching completes to verify final conclusions.

Do I need GitHub CLI authentication to monitor CI pipeline failures?

Yes, you need authenticated GitHub CLI access to monitor CI pipeline failures. This Skill relies on gh CLI commands like gh run list and gh run view to enumerate runs and extract job-level diagnostics for GitHub Actions workflows.

What is the best way to diagnose CI failures across multiple triggered workflows?

The best way to diagnose CI failures across multiple triggered workflows is to surface job-level diagnostics for the current branch. This Skill lists all recent workflow runs, identifies failures, and extracts the specific failing steps to streamline root cause analysis.