跳到正文
cccskills
免费在 GitHub 公开

gha

Investigate failed GitHub Actions jobs using logs and recent runs. Receive a report explaining the actual failure trigger, recurrence, any verified breaking commit, and existing pull requests that may fix the issue.

中文简介正在准备中。当前显示英语简介。

原文查看原文说明

Analyze GitHub Actions failures and identify root causes

集成工具GitHub
查看安装方法

适用场景

  • Finding the actual cause of a failed job
  • Checking whether failures are intermittent or recurring
  • Identifying the commit that introduced a failure
  • Finding existing pull requests that address the issue

包含的文件(1)

  • SKILL.md2.5 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

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 confidence
  4. 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
  5. 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)

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Create a new Claude Code session from the later half of the current conversation. Keep recent work while reducing conversation tokens, then receive a command to resume the copied session directly.

中文简介正在准备中。当前显示英语简介。

  • Continuing a long conversation with its later half
  • Reducing tokens while keeping recent work
  • Resuming a copied session with a direct command
ykdojo/claude-code-tips1万2026年9月25日 更新

handoff

免费

Create or update a HANDOFF.md document with the goal, progress, successful and failed approaches, and next steps. It gives an agent in a fresh conversation the context needed to continue the work.

中文简介正在准备中。当前显示英语简介。

  • Preparing to continue work in a fresh conversation
  • Handing ongoing work to another agent
  • Recording approaches that failed
ykdojo/claude-code-tips1万2026年9月25日 更新

Summarize popular Hacker News stories or find discussions on a specific topic. Get article highlights, scores, comment counts, and recurring discussion themes, including agreement, criticism, and related debates.

中文简介正在准备中。当前显示英语简介。

  • Reviewing the top ten Hacker News stories
  • Summarizing an article and its discussion
  • Finding Hacker News discussions on a topic
ykdojo/claude-code-tips1万2026年9月25日 更新

Search across public and private GitHub repositories using local copies and ripgrep, a text search tool. Find which repository or file contains an implementation, phrase, or setting, with results drawn from the default branch.

中文简介正在准备中。当前显示英语简介。

  • Find which repository contains an implementation
  • Locate configuration files across repositories
  • Search private repositories for a phrase
ykdojo/claude-code-tips1万2026年9月25日 更新

Create a new Claude Code session containing only the last quarter of the current conversation. Preserve the most recent work, reduce conversation tokens, and get a command to resume the copied session directly.

中文简介正在准备中。当前显示英语简介。

  • Continuing with only the last quarter of a conversation
  • Reducing tokens while keeping the most recent work
  • Resuming a copied session with a direct command
ykdojo/claude-code-tips1万2026年9月25日 更新

Retrieve Reddit posts and comments through a browser session for topic research. Search within communities, inspect popular or recent posts, and extract titles, scores, and replies, with procedures for handling blocked access and request limits.

中文简介正在准备中。当前显示英语简介。

  • Research a topic within a subreddit
  • Read a post and its comments
  • Check recent or popular posts
ykdojo/claude-code-tips1万2026年9月25日 更新

查看 ykdojo 的全部技能

报告此技能的问题