From skills
Use when you need to know whether a branch or PR is ready and what to act on next — CI status, review state, merge conflicts, unresolved threads. Covers gathering the signals with gh, watching in-flight CI to completion, and turning the state into the next action.
How this skill is triggered — by the user, by Claude, or both
Slash command
/skills:assessing-pr-readinessThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The job an agent actually has when it looks at a branch or PR is not "is CI green?" — it's **what's actionable right now, and what should happen next?** That spans CI, reviews, merge state, and open threads. This skill is how to gather those signals cheaply and turn them into a decision.
The job an agent actually has when it looks at a branch or PR is not "is CI green?" — it's what's actionable right now, and what should happen next? That spans CI, reviews, merge state, and open threads. This skill is how to gather those signals cheaply and turn them into a decision.
Fire when any of these are true:
Gather these for the branch/PR (most blocking first). Don't stop at CI; a green PR with changes requested is not ready.
CHANGES_REQUESTED blocks; APPROVED clears; empty means review hasn't happened (a comment-only review leaves it empty — read the comments).DIRTY/behind), draft status, or branch protection not satisfied.One PR-level read covers most of it:
gh pr view <pr-or-branch> --json state,isDraft,reviewDecision,mergeStateStatus,statusCheckRollup,reviewRequests
gh pr checks <pr> # per-check pass/fail with links
For a branch with no PR yet, read CI directly:
gh run list --branch <branch> --limit 20 --json databaseId,name,status,conclusion,event
Filter to the most recent run per workflow (several can run on one push; you want the latest of each). If there are zero runs, say CI isn't set up and move on.
When a run is still going and the point is to wait:
gh run watch <run-id> — it streams progress without dumping logs into context. Watch multiple in-flight runs in parallel.gh run watch isn't available, poll gh run view <id> --json status,conclusion — but no faster than once every 30 seconds; faster burns API quota and context cache for nothing./loop skill (e.g. /loop 5m) instead of a tight poll.For any failure, pull just the failing job's tail (gh run view <id> --log-failed) and extract the actual error — don't paste the whole log; cite the URL for the rest.
| State | Next action |
|---|---|
| CI failing | Read the failing log tail, find the real error, fix. Don't auto-rerun without being asked. |
| CI pending | Watch to completion (above); report when done. |
| Changes requested / open threads | Address the findings (see [[receiving-code-review]]); don't merge over them. |
| Merge conflict / behind base | Rebase or merge the base in; resolve, re-push. |
| Draft | It's not up for review yet — mark ready only when it is. |
| Approved + green + clean + threads resolved | It's ready. Surface that; merging is a separate, confirmed action. |
Report the state as a short summary plus the single most important next action — not a wall of check output.
gh run watch, or /loop for recurring checks.reviewDecision as "no feedback". A comment-only review leaves it empty — read the comments before concluding nothing's there.Guides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.
npx claudepluginhub thomasfosterau/skills --plugin skills