본문으로 건너뛰기
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(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

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 / 1,000자

이 양식은 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의 스킬 모두 보기

이 스킬의 문제 신고