Monitor GitHub Actions workflow runs and extract failure diagnostics. Use when watching CI after a push, checking workflow status, or investigating failed runs. Identifies failing jobs, extracts relevant error output, and returns a concise summary.
Monitors GitHub Actions workflows and extracts concise failure diagnostics from job logs.
npx claudepluginhub bendrucker/claudeThis skill is limited to using the following tools:
references/log-parsing.mdMonitor GitHub Actions and extract failure diagnostics. Extract only: find the failures and present them concisely. Do not analyze root causes or suggest fixes.
$ARGUMENTS
If no run ID or PR is specified, use the current branch.
!gh run list --branch $(git branch --show-current) --limit 5 --json databaseId,status,conclusion,displayTitle,workflowName 2>/dev/null || echo "[]"
From the recent runs above, identify the most relevant run (latest, or matching the target). If the run is still in progress, use gh run watch <id> to wait for completion.
gh run view <run-id> --json jobs --jq '[.jobs[] | select(.conclusion == "failure") | {name, databaseId, conclusion}]'
For each failing job, fetch its log:
gh run view --log --job <job-id>
Parse the log output for failure-relevant sections. See references/log-parsing.md for CI-specific log structure.
If the full job log is still too large, try --log-failed on the specific job:
gh run view --log-failed --job <job-id>
When multiple jobs fail, fetch logs for each job in separate parallel Bash calls.
For each failed job, report:
Keep the total output concise. The parent conversation will use this to investigate.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.