github-actions

Diagnose GitHub Actions workflow failures from run statuses and logs.

Updated Jan 2, 2026
One-click install
npx skills add https://github.com/Cogni-AI-OU/xero-fin-ops --skill github-actions-cogni-ai-ou
Or copy as Structured Prompt for Agentā–¼
Please help me install this Agent Skill.
Skill: github-actions
Source: https://github.com/Cogni-AI-OU/xero-fin-ops/tree/main/.github/skills/github-actions
Command: npx skills add https://github.com/Cogni-AI-OU/xero-fin-ops --skill github-actions-cogni-ai-ou

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnose GitHub Actions workflow failures by retrieving run statuses and logs using MCP tools or gh CLI.

Core Features & Use Cases

  • Automated diagnosis: Retrieve run details, status, and logs to pinpoint failure causes.
  • Multiple tooling paths: Prefer MCP tooling when available, with a fallback to gh CLI for authenticated environments.
  • Use Case: When a workflow run shows a failure, provide step-level failure context and suggested fixes based on logs.

Quick Start

Provide an actionable diagnosis for a failing GitHub Actions workflow using the provided run URL.

Frequently Asked Questions about github-actions

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

FAQPage Schema
How do I diagnose GitHub Actions workflow failures from run logs?ā–¼

To diagnose GitHub Actions workflow failures, retrieve the run status and logs via MCP tools or gh CLI to pinpoint step-level failure causes. It provides evidence-based root-cause extraction by analyzing step-level logs from failing CI workflows.

What is the best way to find the root cause of a red status check in GitHub Actions?ā–¼

Finding the root cause of a red status check involves retrieving job details and step-level logs using MCP tooling, or falling back to the gh CLI in authenticated environments. This approach applies evidence-based extraction to identify the exact failing step and suggest fixes.

Can I use the gh CLI to retrieve GitHub Actions run details when MCP tools are unavailable?ā–¼

Yes, you can use the gh CLI to retrieve GitHub Actions run details when MCP tools are unavailable. The Skill prefers MCP tooling for job details but supports falling back to the gh CLI for authenticated environments to fetch logs and diagnose failures.

How do I get step-level context for a failing GitHub Actions job?ā–¼

To get step-level context for a failing GitHub Actions job, provide the run URL to retrieve specific job details and logs. The Skill extracts step-level failure context from these logs to deliver actionable diagnostics and suggested fixes for the failed workflow.

Do I need an authenticated environment to diagnose GitHub Actions CI errors?ā–¼

You need an authenticated environment to diagnose GitHub Actions CI errors if you are using the gh CLI fallback path. If MCP tooling is available, it is the preferred method for retrieving run statuses and logs without requiring separate CLI authentication setup.