gha

Solid

Analyze GitHub Actions failures and identify root causes

Code & Development 8,472 stars 639 forks Updated 2 weeks ago NOASSERTION

Install

View on GitHub

Quality Score: 84/100

Stars 20%
100
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

Investigate this GitHub Actions URL: $ARGUMENTS Use the gh CLI to analyze this workflow run. Your investigation should: 1. **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 2. **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? 3. **Identify breaking commit** (if there's a pattern of failures for the specific job): - 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 confidenc...

Details

Author
ykdojo
Repository
ykdojo/claude-code-tips
Created
5 months ago
Last Updated
2 weeks ago
Language
JavaScript
License
NOASSERTION

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

DevOps & Infrastructure Solid

gh-fix-ci

Inspect GitHub PR checks with gh, pull failing GitHub Actions logs, summarize failure context, then create a fix plan and implement after user approval. Use when a user asks to debug or fix failing PR CI/CD checks on GitHub Actions and wants a plan + code changes; for external checks (e.g., Buildkite), only report the details URL and mark them out of scope.

27 Updated 6 days ago
OutlineDriven
Code & Development Solid

github-actions-docs

Use when users ask how to write, explain, customize, migrate, secure, or troubleshoot GitHub Actions workflows, workflow syntax, triggers, matrices, runners, reusable workflows, artifacts, caching, secrets, OIDC, deployments, custom actions, or Actions Runner Controller, especially when they need official GitHub documentation, exact links, or docs-grounded YAML guidance.

56 Updated 1 months ago
xixu-me
AI & Automation Featured

agentic-actions-auditor

Audits GitHub Actions workflows for security vulnerabilities in AI agent integrations including Claude Code Action, Gemini CLI, OpenAI Codex, and GitHub AI Inference. Detects attack vectors where attacker-controlled input reaches AI agents running in CI/CD pipelines, including env var intermediary patterns, direct expression injection, dangerous sandbox configurations, and wildcard user allowlists. Use when reviewing workflow files that invoke AI coding agents, auditing CI/CD pipeline security for prompt injection risks, or evaluating agentic action configurations.

4,425 Updated 1 months ago
trailofbits
Code & Development Solid

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]

95 Updated 1 months ago
cohen-liel