← ClaudeAtlas

github-clilisted

gh CLI patterns, JSON field discovery, PR check interpretation, label management, merge settings verification, CodeQL/GHAS gating.
juan294/cc-rpi · ★ 5 · Code & Development · score 77
Install: claude install-skill juan294/cc-rpi
# GitHub CLI ## JSON Field Discovery Wrong -- guess field names: ```bash gh pr checks 42 --json conclusion # Unknown field ``` Right -- discover fields first: ```bash gh pr checks 42 --json 2>&1 | head -5 ``` ## PR Check Interpretation Wrong -- exit code 0 means passed, raw output is readable: ```bash gh pr checks 42 # exit 0 but checks still pending; "review: fail" looks like CI ``` Right -- use structured JSON, filter review, or --watch: ```bash gh pr checks 42 --json name,state,conclusion | jq '.[] | select(.name != "review")' gh pr checks 42 --watch ``` ## Release vs PR Flags Wrong -- --body is for pr/issue create, not release: ```bash gh release create v1.0.0 --body "notes" ``` Right -- releases use --notes: ```bash gh release create v1.0.0 --notes "notes" ``` ## Label and Merge Settings Wrong -- assume labels exist and merge method is allowed: ```bash gh issue create --label "chore" --title "Fix" # label not found gh pr merge 42 --merge # method not allowed ``` Right -- check or create first: ```bash gh label list && gh label create "chore" --color "ededed" gh api repos/{owner}/{repo} --jq '.allow_squash_merge, .allow_merge_commit' ``` When creating multiple issues, create them sequentially, not as parallel tool calls -- a batch of parallel `gh issue create` calls that all hit the same missing label fail together instead of surfacing once. ## Deprecated Projects (Classic) API Wrong -- an older `gh` version queries a remo