🎯

gha

🎯Skill

from ykdojo/claude-code-tips

What it does

Investigates GitHub Actions workflow failures by analyzing logs, run history, identifying root causes, and checking for potential fixes.

📦

Part of

ykdojo/claude-code-tips(7 items)

gha

Installation

npm installInstall npm package

npm install -g cc-safe

npxRun with npx

npx cc-safe .

DockerRun with Docker

docker run --privileged

Local ServerRun MCP server locally

claude mcp add -s user playwright npx @playwright/mcp@latest

ConfigurationMCP configuration (may be incomplete)

{
  "attribution": {
    "commit": "",
    "pr": ""
  }
}
```

Setting both to e...

📖 Extracted from docs: ykdojo/claude-code-tips

Need more details? View full documentation on GitHub →

1Installs

AddedFeb 4, 2026

View on GitHub Back to Skills

Skill Details

SKILL.md

Analyze GitHub Actions failures and identify root causes

Overview

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= to get run IDs, then gh run view --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?

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 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 "" 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)

More from this repository6

🏪

ykdojo-claude-code-tips🏪Marketplace

40+ tips for getting the most out of Claude Code, from basics to advanced - includes a custom status line script, cutting the system prompt in half, using Gemini CLI as Claude Code's minion, and Claude Code running itself in a container. Also includes the dx plugin.

🎯

reddit-fetch🎯Skill

reddit-fetch skill from ykdojo/claude-code-tips

🎯

review-claudemd🎯Skill

Analyzes recent conversation history to identify improvements for CLAUDE.md files, suggesting rule reinforcements and new guidelines.

🎯

clone🎯Skill

Clones the current conversation, enabling users to explore alternative approaches without losing the original context.

🎯

handoff🎯Skill

Generates a comprehensive handoff document to ensure smooth knowledge transfer and continuity of work across different agents.

🎯

half-clone🎯Skill

Clones the latter half of the current conversation, reducing context while preserving recent work and token efficiency.