菜单
Inspect GitHub Actions runs, analyze logs, debug failures. Use when investigating CI/CD failures, checking workflow status, or debugging GitHub Actions issues.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/laurigates/claude-plugins --skill github-actions-inspection命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
基于 SOC 职业分类
| created | "2025-12-16T00:00:00.000Z" |
| modified | "2026-04-25T00:00:00.000Z" |
| reviewed | "2026-04-25T00:00:00.000Z" |
| name | github-actions-inspection |
| description | Inspect GitHub Actions runs, analyze logs, debug failures. Use when investigating CI/CD failures, checking workflow status, or debugging GitHub Actions issues. |
| user-invocable | false |
| allowed-tools | Bash, Read, Grep, Glob, mcp__github |
| Use this skill when... | Use the linked sibling instead when... |
|---|---|
Pulling status, logs, and conclusions from gh run for a failing workflow |
| Authoring or modifying a workflow YAML file — see claude-code-github-workflows |
| Diagnosing flaky tests, timeouts, or auth-permission errors in a CI run | Searching upstream OSS issues for a library bug — see github-issue-search |
| Rerunning failed jobs, watching in-progress runs, or extracting error lines | Building a workflow that auto-fixes CI failures — see github-workflow-auto-fix |
Expert knowledge for inspecting, debugging, and troubleshooting GitHub Actions workflow runs using gh CLI and GitHub API.
For detailed examples, advanced patterns, and best practices, see REFERENCE.md.
Workflow Run Inspection
Log Analysis
Debugging Workflows
# List all workflow runs
gh run list
# List runs for specific workflow
gh run list --workflow=ci.yml
# Filter by status
gh run list --status=failure
gh run list --status=in_progress
# Filter by branch
gh run list --branch=main
# Combine filters
gh run list --workflow=ci.yml --status=failure --limit 5
# JSON output for parsing
gh run list --json databaseId,status,conclusion,name,createdAt,headBranch
# View specific run
gh run view <run-id>
# View failed logs only
gh run view <run-id> --log-failed
# View specific job
gh run view <run-id> --job=<job-id>
# JSON output
gh run view <run-id> --json status,conclusion,jobs,startedAt,updatedAt
# Download logs for run
gh run download <run-id>
# View failed step logs only
gh run view <run-id> --log-failed
# Extract specific job logs
gh api repos/:owner/:repo/actions/runs/<run-id>/logs | less
# Watch workflow progress
gh run watch <run-id>
# Watch with exit status
gh run watch <run-id> --exit-status
# Rerun entire workflow
gh run rerun <run-id>
# Rerun only failed jobs
gh run rerun <run-id> --failed
# Rerun with debug logging
gh run rerun <run-id> --debug
# Cancel specific run
gh run cancel <run-id>
# Get last 10 failed runs
gh run list --status=failure --limit 10
# Get failures with details
gh run list --workflow=ci.yml --status=failure --limit 5 \
--json databaseId,conclusion,name,createdAt,headBranch,headSha
# Get runs for specific commit
gh run list --commit=<sha>
# Find tests that sometimes pass
gh run list --workflow=test.yml --limit 20 --json conclusion \
| jq 'group_by(.conclusion) | map({conclusion: .[0].conclusion, count: length})'
# View failed logs
gh run view <run-id> --log-failed
# Extract error lines
gh run view <run-id> --log-failed | grep -i "error\|failed\|exception"
# Parse JSON for errors
gh api repos/:owner/:repo/actions/runs/<run-id>/jobs \
| jq '.jobs[] | select(.conclusion == "failure") | {name, steps: [.steps[] | select(.conclusion == "failure")]}'
# Get run duration
gh run view <run-id> --json startedAt,completedAt,durationMs
# Compare run times
gh run list --workflow=ci.yml --limit 10 \
--json databaseId,createdAt,updatedAt,durationMs \
| jq '.[] | {id: .databaseId, duration_min: (.durationMs / 60000)}'
# Check current status
gh run list --status=in_progress
# Summary of run statuses
gh run list --limit 50 --json conclusion \
| jq 'group_by(.conclusion) | map({conclusion: .[0].conclusion, count: length})'
| Pattern | Symptoms | Quick Fix |
|---|---|---|
| Authentication | "403 Forbidden", "Resource not accessible" | Check GITHUB_TOKEN scope, workflow permissions |
| Timeout | "exceeded maximum execution time" | Increase timeout-minutes, split parallel jobs |
| Flaky tests | Same test passes/fails inconsistently | Fix race conditions, mock external deps |
| Dependency install | "Could not find package", "Version conflict" | Lock versions, use cache |
| Environment | "Command not found", "Module not found" | Verify setup steps, check runner version |
| Resource constraints | "out of disk space", "Process killed" | Clean artifacts, increase runner size |
| Context | Command |
|---|---|
| Quick failure check | gh run list --status=failure --limit 5 --json databaseId,conclusion,name |
| Failed logs only | gh run view <id> --log-failed |
| JSON run details | gh run view <id> --json status,conclusion,jobs |
| Failure rate | gh run list --limit 50 --json conclusion | jq 'group_by(.conclusion)' |
| Rerun failed only | gh run rerun <id> --failed |
gh run list - List workflow runsgh run view <id> - View run detailsgh run watch <id> - Watch run progressgh run download <id> - Download logs/artifactsgh run rerun <id> - Rerun workflowgh run cancel <id> - Cancel running workflow--workflow=<name> - Specific workflow--status=<status> - Filter by status (in_progress, completed, queued, waiting)--conclusion=<conclusion> - Filter by conclusion (success, failure, cancelled, skipped)--branch=<branch> - Specific branch--event=<event> - Specific trigger event--limit=<n> - Limit results--json <fields> - JSON outputqueued - Waiting to startin_progress - Currently runningcompleted - Finished (check conclusion)waiting - Waiting for approvalsuccess - All jobs succeededfailure - At least one job failedcancelled - Manually cancelledskipped - Skipped (conditional)timed_out - Exceeded time limitThis skill complements:
Install, configure and troubleshoot MCP servers. Use when adding/enabling servers, editing .mcp.json, fixing OAuth, or when a server runs stale code after an upstream fix.
FinOps snapshot — org billing, workflow stats, cache usage. Use when you want a high-level view of CI spending or workflow health before diving deeper.
GitHub Actions billing, workflow efficiency, and waste analysis at org or repo level. Use when investigating CI/CD costs, wasted runs, or optimizing triggers.