gh-cli

name	gh-cli
description	Use GitHub through the `gh` CLI in the sandbox. Use when the user asks to inspect repositories, clone code, search issues or pull requests, review runs, create branches, or prepare pull requests.

GitHub CLI

The sandbox template preinstalls gh and git. The authenticated GitHub account is determined by the configured GITHUB_TOKEN.

First Checks

gh auth status
gh repo view --json nameWithOwner,url,defaultBranchRef

If auth fails, stop and say GitHub credentials are not available in the sandbox. Never ask the user to paste tokens into Slack or files.

Workflow

1. Identify the repo with gh repo view, a URL from the user, or owner/repo.
2. For reads, use gh repo view, gh issue, gh pr, gh run, gh search, or gh api.
3. Check viewerPermission before writing. Use a fork when the authenticated account cannot push to the target repository.
4. For writes, summarize the intended change first when it affects public GitHub state.
5. Report URLs for created or modified issues, PRs, releases, workflow runs, and repos.

References

• Common repository, issue, PR, run, and search commands: Operations.
• gh api patterns for REST and GraphQL when the typed commands are missing a feature: API.
• Safe contribution flow for cloning, branching, committing, and opening PRs: Contribution Flow.