Skip to content

Search skills.../

Agent Skill Search Engine

Search

Search
Categories
Occupations

About

About
Privacy
Terms

© 2026 Skills Pool. All rights reserved.

Gha | Skills Pool

Skill File

Gha

Analyze GitHub Actions failures and identify root causes

ykdojo7,788 starsFeb 1, 2026

Occupation: Software Quality Assurance Analysts and Testers
Categories: CI/CD

Skill Content

Investigate this GitHub Actions URL: $ARGUMENTS

Use the gh CLI to analyze this workflow run. Your investigation should:

Get basic info & identify actual failure:
- What workflow/job failed, when, and on which commit?
- CRITICAL: Read the full logs carefully to find what SPECIFICALLY caused the exit code 1
- Distinguish between warnings/non-fatal errors vs actual failures
- Look for patterns like "failing:", "fatal:", or script logic that determines when to exit 1
- If you see both "non-fatal" and "fatal" errors, focus on what actually caused the failure
Check flakiness: Check the past 10-20 runs of THE EXACT SAME failing job:
- IMPORTANT: If a workflow has multiple jobs, you must check history for the SPECIFIC JOB that failed, not just the workflow
- Use gh run list --workflow=<workflow-name> to get run IDs, then gh run view <run-id> --json jobs to check the specific job's status
- Is this a one-time failure or recurring pattern for THIS SPECIFIC JOB?
- What's the success rate for THIS JOB recently?
- When did THIS JOB last pass?
(if there's a pattern of failures for the specific job):

Related Skills

Quick Install

Gha

npx skillvault add ykdojo/ykdojo-claude-code-tips-skills-gha-skill-md

Download Skill Open repository

Author: ykdojo
stars: 7,788
Updated: Feb 1, 2026
Occupation

Identify breaking commit

Find the first run where THIS SPECIFIC JOB failed and the last run where it passed
Identify the commit that introduced the failure
Verify by checking: does THIS JOB fail in ALL runs after that commit? Does it pass in ALL runs before?
If verified, report the breaking commit with high confidence

Root cause: Based on logs, history, and any breaking commit, what's the likely cause?

Focus on what ACTUALLY caused the failure (not just any errors you see)
Verify your hypothesis against the logs and failure logic

Check for existing fix PRs: Search for open PRs that might already address this issue:

Use gh pr list --state open --search "<keywords>" with relevant error messages or file names
Check if any open PR modifies the failing file/workflow
If a fix PR exists, note it in your report and skip the recommendation section

Write a final report with:

Summary of failure (what specifically triggered the exit code 1)
Flakiness assessment (one-time vs recurring, success rate)
Breaking commit (if identified and verified)
Root cause analysis (based on the ACTUAL failure trigger)
Existing fix PR (if found - include PR number and link)
Recommendation (skip if fix PR already exists)

Github

GitHub operations via `gh` CLI: issues, PRs, CI runs, code review, API queries. Use when: (1) checking PR status or CI, (2) creating/commenting on issues, (3) listing/filtering PRs or issues, (4) viewing run logs. NOT for: complex web UI interactions requiring manual browser flows (use browser tooling when available), bulk operations across many repos (script with gh api), or when gh auth is not configured.

Security Triage

Triage GitHub security advisories for OpenClaw with high-confidence close/keep decisions, exact tag and commit verification, trust-model checks, optional hardening notes, and a final reply ready to post and copy to clipboard.

Openclaw Parallels Smoke

End-to-end Parallels smoke, upgrade, and rerun workflow for OpenClaw across macOS, Windows, and Linux guests. Use when Codex needs to run, rerun, debug, or interpret VM-based install, onboarding, gateway smoke tests, latest-release-to-main upgrade checks, fresh snapshot retests, or optional Discord roundtrip verification under Parallels.

Gh Issues

Fetch GitHub issues, spawn sub-agents to implement fixes and open PRs, then monitor and address PR review comments. Usage: /gh-issues [owner/repo] [--label bug] [--limit 5] [--milestone v1.0] [--assignee @me] [--fork user/repo] [--watch] [--interval 5] [--reviews-only] [--cron] [--dry-run] [--model glm-5] [--notify-channel -1002381931352]

Openclaw Ghsa Maintainer

Maintainer workflow for OpenClaw GitHub Security Advisories (GHSA). Use when Codex needs to inspect, patch, validate, or publish a repo advisory, verify private-fork state, prepare advisory Markdown or JSON payloads safely, handle GHSA API-specific publish constraints, or confirm advisory publish success.

Author Contributions

Identify all files a specific author contributed to on a branch vs its upstream, tracing code through renames. Use when asked who edited what, what code an author contributed, or to audit authorship before a merge. This skill should be run as a subagent — it performs many git operations and returns a concise table.

microsoft184.0k

Software Quality Assurance Analysts and Testers