gh

Read GitHub Actions run status and logs via gh CLI as structured JSON.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/flesler/dotfiles --skill gh-flesler
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh
Source: https://github.com/flesler/dotfiles/tree/main/home/.cursor/skills/gh
Command: npx skills add https://github.com/flesler/dotfiles --skill gh-flesler

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Reading GitHub Actions run statuses and logs is often manual and time-consuming. This Skill provides a focused, read-only interface via gh to quickly diagnose CI failures and monitor workflow progress.

Core Features & Use Cases

  • Read latest run status with gh run list
  • Inspect individual runs and their jobs with gh run view
  • Fetch and tail logs with gh run view --log or --log-failed for debugging across repositories

Quick Start

Ask the AI to fetch the latest GitHub Actions run status and logs for a given repository using gh.

Frequently Asked Questions about gh

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

FAQPage Schema
How do I read GitHub Actions logs to debug CI failures?

Reading GitHub Actions logs for CI failures is automated by using the GitHub CLI to fetch run statuses and tail failed job outputs. This Skill leverages gh commands to inspect individual jobs and stream logs directly for efficient debugging.

Can I monitor the latest GitHub Actions workflow run status across multiple repositories?

Yes, monitoring the latest GitHub Actions workflow run status across multiple repositories is possible by executing gh run list commands. This Skill automates fetching these statuses to provide a structured overview of your current CI runs.

Do I need the GitHub CLI installed and authenticated to view CI run statuses?

Yes, the GitHub CLI must be installed and authenticated to view CI run statuses. This Skill acts as a focused read-only interface that directly executes gh commands to retrieve workflow data from your authenticated environment.

What is the best way to inspect individual GitHub Actions jobs and their logs?

The best way to inspect individual GitHub Actions jobs and their logs is by automating gh run view commands. This Skill retrieves specific job details and streams failed logs, outputting structured JSON suitable for downstream tools like jq.

How do I get structured JSON output from GitHub Actions logs for downstream processing?

You get structured JSON output from GitHub Actions logs by running automated gh commands for workflow status and log retrieval. This Skill formats the CI data into JSON, making it immediately suitable for filtering and processing with tools like jq.