Content
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
An efficient, highly actionable gh CLI reference that assumes Claude's competence and is well organized. Its only gap is the absence of validation/confirmation checkpoints around destructive operations (merge, close, rerun).
Suggestions
Add an explicit pre-flight check before destructive commands — e.g. run `gh pr view <n> --json mergeable,reviewDecision` and confirm CI is green before `gh pr merge`, mirroring the validate-then-proceed pattern.
Add a brief confirmation/verification note for batch-ish or irreversible actions (issue close, run rerun), such as re-checking status after the action completes.
Reduce the light redundancy between the description's "NOT for" list and the body's "When NOT to Use" section by keeping the body version focused on command-routing guidance rather than restating scope.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Lean command snippets with terse comments and no explanation of what GitHub/PRs/CI are; every token earns its place and it assumes Claude's competence. | 3 / 3 |
Actionability | Fully executable, copy-paste-ready commands throughout — e.g. "gh pr checks 55 --repo owner/repo", "gh run view <run-id> --log-failed" — plus concrete --jq filter templates. | 3 / 3 |
Workflow Clarity | Scoping (When to Use / NOT to Use) and the setup login→verify sequence are clear, but destructive operations like "gh pr merge 55 --squash", "gh issue close 42", and "gh run rerun" are shown with no pre-flight validation or confirmation checkpoint, which caps the score per the rubric. | 2 / 3 |
Progressive Disclosure | A single self-contained reference with clearly organized sections (Setup, Common Commands sub-sections, Templates, Notes) and no nested/deep references; for a reference skill the inline command examples are appropriately placed. | 3 / 3 |
Total | 11 / 12 Passed |