ci

List and inspect GitHub Actions workflow runs for the current branch.

3|Updated Sep 5, 2021
One-click install
npx skills add https://github.com/aviralmansingka/dotfiles --skill ci-aviralmansingka
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ci
Source: https://github.com/aviralmansingka/dotfiles/tree/main/claude/.claude/skills/ci
Command: npx skills add https://github.com/aviralmansingka/dotfiles --skill ci-aviralmansingka

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you quickly understand whether your current GitHub Actions build is healthy, failing, or still running, and gives you the exact logs to debug issues without manually browsing the UI.

Core Features & Use Cases

  • Branch-focused CI status: Uses your current git branch to list the most recent runs and determine the current build state.
  • Workflow run inspection: Opens the latest run details and can drill into a specific run ID for targeted investigation.
  • Failure and log retrieval: Fetches failed job logs automatically to speed up root-cause analysis.
  • Operational actions: Supports watching a run in progress and rerunning failed jobs or an entire workflow.

Quick Start

Type /ci to fetch the latest recent CI runs for your current branch and automatically show details if there is a failing or in-progress run.

Frequently Asked Questions about ci

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

FAQPage Schema
How do I check GitHub Actions CI status for my current git branch?

To check GitHub Actions CI status for your current git branch, use this Skill to list recent workflow runs and automatically inspect details for failing or in-progress runs. It requires the GitHub CLI to fetch and display run statuses scoped to the active branch.

How do I get failed job logs from GitHub Actions workflow runs?

To get failed job logs from GitHub Actions workflow runs, this Skill automatically fetches failed job logs during run inspection. It uses the GitHub CLI to retrieve and surface the relevant log output for root-cause analysis.

Can I rerun failed GitHub Actions workflows or jobs from the command line?

Yes, you can rerun failed GitHub Actions workflows or jobs from the command line using this Skill. It supports rerunning only failed jobs or executing an entire workflow run again through GitHub CLI operations scoped to specific run IDs.

Do I need the GitHub CLI to diagnose GitHub Actions CI status?

Yes, you need the GitHub CLI installed to diagnose GitHub Actions CI status with this Skill. It requires the gh command-line tool to execute run listing, log retrieval, watching, and rerun operations for your active git branch.

What is the best way to debug GitHub Actions CI failures without browsing the UI?

The best way to debug GitHub Actions CI failures without browsing the UI is using this Skill to fetch recent branch runs, drill into specific run IDs, and automatically retrieve failed job logs for targeted root-cause analysis.