gh-cli

Debug GitHub Actions runs and retrieve release assets via gh CLI.

2|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/dededecline/dotfiles --skill gh-cli-dededecline
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-cli
Source: https://github.com/dededecline/dotfiles/tree/main/claude/skills/gh-cli
Command: npx skills add https://github.com/dededecline/dotfiles --skill gh-cli-dededecline

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Makes debugging CI failures and retrieving release assets straightforward by providing concise commands to list, inspect, and act on GitHub Actions runs and releases, eliminating manual web UI navigation and repetitive command construction.

Core Features & Use Cases

  • Inspect Workflow Runs: List recent runs, filter by status, workflow, or branch, and view run summaries.
  • Diagnose Failures: Fetch failed logs, view job details, and download artifacts for debugging.
  • Manage Workflows: Re-run workflows, cancel runs, watch runs in real time, and trigger workflows with inputs.
  • Releases & Repository Ops: List and view releases, download release assets, and clone or view repositories.
  • Automation & Scripting: Emit structured JSON fields for integration with jq and other automation tools.
  • Use Case: When a CI build fails on the main branch, quickly identify the failing job, download its logs, and re-run only the failed jobs to validate a fix.

Quick Start

Authenticate with gh, list recent failed workflow runs, inspect the failed run's logs, and download any artifacts for local debugging.

Frequently Asked Questions about gh-cli

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

FAQPage Schema
How do I debug failed GitHub Actions runs from the command line?

Debug failed GitHub Actions runs by using gh CLI to list recent runs, filter by failed status, fetch specific job logs, and download artifacts for local inspection. This eliminates manual web UI navigation and repetitive command construction.

Can I use gh CLI to download release assets for automation?

Yes, gh CLI retrieves release assets by listing and viewing repository releases, then downloading specific assets directly. It supports non-interactive automation through GH_TOKEN or GITHUB_TOKEN authentication, enabling automated release asset retrieval.

How do I filter GitHub Actions workflow runs by branch or status?

Filter GitHub Actions workflow runs by branch, status, or workflow name using gh CLI commands. The Skill provides concise commands to list and inspect runs matching specific criteria, emitting structured JSON fields for integration with jq and other automation tools.

Do I need authenticated gh CLI access for non-interactive automation?

Yes, authenticated gh CLI access is required for non-interactive automation. You must provide tokens like GH_TOKEN or GITHUB_TOKEN to authenticate, enabling automated workflow management, release retrieval, and repository operations without manual login prompts.

What's the best way to re-run only failed jobs in a GitHub Actions workflow?

Re-run only failed jobs in a GitHub Actions workflow using gh CLI commands to identify the failing job, then trigger a targeted re-run. This validates fixes quickly without re-executing the entire workflow, streamlining CI debugging.

Does gh CLI support JSON output for scripting and jq integration?

Yes, gh CLI supports structured JSON output for scripting and jq integration. The Skill emits specific JSON fields for workflow runs, logs, and releases, enabling seamless integration with automation tools and pipeline scripts.