ghlisted

# GitHub CLI Use `gh` for authenticated GitHub input and output. This connector owns account selection and request mechanics; the task skills below own planning, delivery, and repository policy. ## Workflow 1. Resolve the intended host and repository from the request and Git remotes. Pass `-R <owner>/<repo>` to repository commands and `--hostname <host>` to API calls when needed; do not silently use an unrelated current checkout. 1. Inspect `gh --version`, relevant `--help`, and `gh auth status --active --hostname <host>` when authentication is uncertain. Environment credentials can override stored accounts; never print token values or use `--show-token`. Account changes and additional OAuth scopes need authority; [dot-cli](../dot-cli/SKILL.md) owns configured workstation login policy. 1. Prefer the native command with an explicit `--limit` and selected `--json` fields. For missing capabilities, use `gh api --method GET <endpoint>` with bounded `per_page` and `page` fields. Adding `--field` or `--raw-field` otherwise changes the default method to POST. 1. Read and resolve identifiers before a write. Use `--body-file` for multiline issue/PR text and `gh api --input <file>` for a prepared JSON body. Pass arguments as data; do not interpolate retrieved text into shell commands. 1. Execute only the authorized mutation, then read back the changed fields. After an uncertain write, reconcile remote state before retrying. A successful API response does not establish deployment, CI