github-actions-logs

Diagnose GitHub Actions workflow logs and summarize failed job runs.

Updated Aug 23, 2026

Search Tags:#automation #workflow #debugging #GitHub Actions #analyze #CI logs

Ready to run

npx skills add https://github.com/dlddu/claude-agent --skill github-actions-logs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: github-actions-logs
Source: https://github.com/dlddu/claude-agent/tree/main/.claude/skills/github-actions-logs
Command: npx skills add https://github.com/dlddu/claude-agent --skill github-actions-logs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps developers diagnose and analyze GitHub Actions workflow logs to quickly identify root causes of CI failures.

Core Features & Use Cases

Retrieve recent workflow runs and statuses to prioritize debugging.
View and summarize logs from failed jobs to pinpoint errors.
Provide quick health checks of workflows across a repository to monitor CI stability.

Quick Start

Use the skill to show the most recent failed workflow and display its logs to investigate the error.

Frequently Asked Questions about github-actions-logs

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

FAQPage Schema

How do I analyze GitHub Actions logs to find the root cause of a CI failure?▼

To analyze GitHub Actions logs, you can retrieve recent workflow runs, inspect failed jobs, and view summarized logs to pinpoint the exact error causing your CI failure. This expedites root-cause investigation.

How do I check the recent status of GitHub Actions workflow runs across a repository?▼

You can check recent GitHub Actions workflow runs by retrieving their statuses across the repository. This provides a quick health check of your workflows to monitor CI stability and prioritize debugging efforts.

Can I use GitHub CLI to view and summarize logs from failed CI jobs?▼

Yes, you can use GitHub CLI (gh) to view and summarize logs from failed CI jobs. The skill requires repository access with an appropriate token to fetch and structure these logs for quick error investigation.

What is the best way to automate GitHub Actions log analysis for debugging?▼

The best way to automate GitHub Actions log analysis is to retrieve workflow runs and output structured results from failed job logs. This allows you to programmatically parse CI errors and expedite root-cause investigation.

Do I need an access token to diagnose GitHub Actions workflow logs?▼

Yes, you need an access token and repository access to diagnose GitHub Actions workflow logs. The skill requires the GitHub CLI (gh) configured with an appropriate token to retrieve runs, jobs, and log data.