Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From github
Monitors GitHub Actions workflow runs, identifies failing jobs, extracts error logs, and summarizes diagnostics. Useful for checking CI status after pushes or investigating failures.
npx claudepluginhub bendrucker/claude --plugin githubHow this skill is triggered — by the user, by Claude, or both
Slash command
/github:actions-monitorhaikuThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Monitor GitHub Actions and extract failure diagnostics. Extract only: find the failures and present them concisely. Do not analyze root causes or suggest fixes.
Inspects GitHub Actions workflow runs using gh CLI: lists runs, checks status, analyzes logs, debugs failures, reruns jobs. Use for CI/CD troubleshooting.
Monitors GitHub Actions workflow runs to completion using blocking `gh run watch` commands, avoiding polling timeouts. Use for CI/CD pipelines, PR checks, and debugging failures.
Manages GitHub Actions workflows via gh CLI: check CI status, list/view/watch/rerun runs and logs.
Share bugs, ideas, or general feedback.
Monitor 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.
!git branch --show-current
Fetch recent runs for the current branch:
gh run list --branch <current-branch> --limit 5 --json databaseId,status,conclusion,displayTitle,workflowName
Query the PR to get the source branch SHA: gh pr view --json headRefOid. Report this as "Source SHA" in the output. Compare against the run's headSha to detect merge queue or other synthetic commit scenarios.
From the recent runs, 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.