GitHub CLI (gh)

This skill makes you fluent with gh: pick the right subcommand, drive it non-interactively, and reach for gh api when a porcelain command can't do the job. Detailed per-command flag references live in references/ — load the one that matches the task instead of guessing flag names.

Operating principles

Run non-interactively by default. Most gh subcommands drop into an interactive prompt when required fields are missing. In an agent session that prompt hangs. So always supply the flags that make a command complete on its own: --title/--body for create commands, a merge strategy (--squash etc.) for gh pr merge, --yes for destructive commands. If a body is long or multi-line, write it to a temp file and pass --body-file <file> (or -F - to read stdin) rather than fighting shell quoting.