Menu
gh CLI patterns, JSON field discovery, PR check interpretation, label management, merge settings verification.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Push accountability, CI monitoring after push, background agent CI verification, verification command sequencing.
Production deployment rules, rollback-first recovery, dependency batching, CI cost awareness, and framework upgrade verification.
Always use when user asks to create, generate, draw, or design a diagram, flowchart, architecture diagram, ER diagram, sequence diagram, class diagram, network diagram, mockup, wireframe, or UI sketch, or mentions draw.io, drawio, drawoi, .drawio files, or diagram export to PNG/SVG/PDF.
Known agent error patterns -- debugging reference for tool failures, git errors, CI issues, and common mistakes. Consult when encountering unexpected behavior, tool errors, or CI failures.
Git recipes, worktree management, push sequences, branch verification, and conflict resolution patterns.
macOS-specific patterns: launchd agent configuration, brew vs pip, zsh regex quirks, file descriptor limits.
| name | GitHub CLI |
| description | gh CLI patterns, JSON field discovery, PR check interpretation, label management, merge settings verification. |
Wrong -- guess field names:
gh pr checks 42 --json conclusion # Unknown field
Right -- discover fields first:
gh pr checks 42 --json 2>&1 | head -5
Wrong -- exit code 0 means passed, raw output is readable:
gh pr checks 42 # exit 0 but checks still pending; "review: fail" looks like CI
Right -- use structured JSON, filter review, or --watch:
gh pr checks 42 --json name,state,conclusion | jq '.[] | select(.name != "review")'
gh pr checks 42 --watch
Wrong -- --body is for pr/issue create, not release:
gh release create v1.0.0 --body "notes"
Right -- releases use --notes:
gh release create v1.0.0 --notes "notes"
Wrong -- assume labels exist and merge method is allowed:
gh issue create --label "chore" --title "Fix" # label not found
gh pr merge 42 --merge # method not allowed
Right -- check or create first:
gh label list && gh label create "chore" --color "ededed"
gh api repos/{owner}/{repo} --jq '.allow_squash_merge, .allow_merge_commit'
Wrong -- create PR when one already exists for this branch:
gh pr create --title "feat: thing"
Right -- check first, edit if exists:
gh pr list --head <branch> --base <base>
# Exists: gh pr edit <number> | New: gh pr create
Wrong -- fabricate repo names or issue numbers (case-sensitive):
gh issue view 42 --repo owner/MyProject
Right -- discover identifiers:
gh repo list owner --json name --limit 50
gh issue list --search "bug in login"