githublisted

Use the `gh` CLI for everything. The user's OAuth access token is exported as `$GH_TOKEN`; `gh` reads it automatically — `gh auth status` will say "not logged in" because gh keeps no config file in the sandbox, but every authenticated subcommand works regardless. `gh --help` and `gh <subcommand> --help` are always current. When unsure, read the help first instead of guessing flags. ## Two ways to call gh — prefer subcommands ### Style A: First-class subcommands — START HERE `gh issue`, `gh pr`, `gh repo`, `gh search`, `gh release`, `gh workflow`, `gh run`, `gh status`, `gh project`, `gh label`, `gh secret`, `gh variable`, `gh gist`. Use these whenever they cover the task; they output formatted text by default and structured JSON via `--json <fields> [--jq <expr>]`. ### Style B: Raw REST / GraphQL via `gh api` `gh api <endpoint>` for REST, `gh api graphql -f query='…'` for GraphQL. Useful when no first-class subcommand exists. Notable flags: - `-X POST|PATCH|PUT|DELETE` — override method (default `GET`, becomes `POST` automatically when `-f`/`-F` is set). - `-f key=value` — string field; `-F key=value` — JSON-typed field (`true`/`123`/`@file.json`); both URL-encode for `GET` and JSON-encode for body methods. - `-q '<jq>'` — same as `--jq`. With a primitive top-level value (string / number) it prints the raw value (no quotes). - `-H 'Accept: application/vnd.github.raw'` — fetch a file's raw bytes instead of the JSON wrapper. - `--paginate` — auto-walk `Link: re