gh-run

Retrieves GitHub Actions run data and failure logs via gh CLI, generating structured reports with severity-filtered details.

Updated May 25, 2024
One-click install
npx skills add https://github.com/gioe/laughtrack --skill gh-run
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-run
Source: https://github.com/gioe/laughtrack/tree/main/.agents/skills/gh-run
Command: npx skills add https://github.com/gioe/laughtrack --skill gh-run

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the inspection of GitHub Actions runs by fetching run metadata and failure logs and rendering an inline, structured report that helps you quickly understand what happened.

Core Features & Use Cases

  • Mode-based exploration: list recent runs across workflows or drill into a single run to view header, workflow, branch, duration, and per-job breakdown.
  • Failure triage & categorization: automatically categorize failure signals (tests, imports, memory, timeouts, scripts) and present concise red-flag lines.
  • Guided remediation: filter logs by level (error, warning, notice, debug) to focus on actionable items and provide guidance for next steps.
  • Use Case: When a failed workflow blocks a release, inspect the latest run to surface the root causes and key failing steps.

Quick Start

Run the gh-run skill to inspect a specific GitHub Actions run or list recent runs and begin diagnosing failures.

Frequently Asked Questions about gh-run

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

FAQPage Schema
How do I view GitHub Actions failure logs to debug a failed CI workflow?

View GitHub Actions failure logs by retrieving run metadata and extracting level-filtered error messages to triage failed CI workflows. This surfaces root causes and key failing steps quickly through an inline structured report of per-job statuses.

What is the best way to list recent GitHub Actions runs across workflows?

Listing recent GitHub Actions runs across workflows is best done by automating gh CLI retrieval to present an inline report. This renders run headers, branches, durations, and per-job breakdowns for quick visibility without manual querying.

Can I filter GitHub Actions logs by level to focus on actionable errors?

Yes, you can filter GitHub Actions logs by level to focus on actionable items during failure triage. Extracting logs by error, warning, notice, or debug levels isolates red-flag lines and provides guidance for next remediation steps.

Does this method require the gh CLI to inspect GitHub Actions runs?

Yes, inspecting GitHub Actions runs requires the gh CLI to fetch run metadata and failure logs. It automates data retrieval and parsing from the CLI to render structured inline reports for incident response and CI/CD debugging.

How are GitHub Actions failure signals categorized during incident response?

GitHub Actions failure signals are categorized during incident response by automatically grouping error messages into tests, imports, memory, timeouts, and scripts. This automatically presents concise red-flag lines to accelerate remediation.