Every section is lean and purposeful. No unnecessary explanations of what gh CLI is or how CI works. The trigger section efficiently explains why gh pr checks is preferred over gh run list. Every token earns its place.

Provides specific, copy-paste-ready gh CLI commands with exact flags and JSON field selectors. The commands section covers all key operations (resolve PR, inspect checks, watch, view logs) with concrete executable examples.

Clear 5-step sequence with explicit decision points (already failed vs pending), a feedback loop (re-check after every push and repeat until green), and guardrails that serve as validation checkpoints (scoped fixes, no --no-verify, flake handling, re-running checks after push).

For a focused, single-purpose skill under 50 lines with no need for external references, the content is well-organized into clear sections (Trigger, Workflow, Commands, Guardrails, Output) that are easy to scan and navigate.

Names the domain (PR checks) and some actions (monitor, fix failures), but doesn't list specific concrete actions like 'analyze CI logs', 'push fixes', 'rerun flaky tests', etc. The phrase 'fix failures until green' is somewhat concrete but still high-level.

The 'what' is reasonably clear (monitor PR checks and fix failures), but there is no explicit 'Use when...' clause or equivalent trigger guidance. The 'when' is only implied by the nature of the task described.

Includes relevant terms like 'PR checks', 'gh pr checks', 'failures', and 'green', but misses common user variations like 'CI', 'pipeline', 'build failing', 'tests failing', 'GitHub Actions', 'check status', or 'PR not passing'.

This is a fairly distinct niche — monitoring PR-attached checks via 'gh pr checks' and iterating until green. It's unlikely to conflict with general coding skills or other CI-related skills due to the specific mention of PR checks and the gh CLI tool.