github

The github_* tools are the gh CLI, already installed and already authenticated on this machine. That is the whole design: gh holds the credentials in the OS keyring, knows which repo the session directory belongs to, paginates, and renders diffs and check runs. Do not write an API client, do not ask the user for a token, and do not go looking for one in the environment.

github_status tells you which account you are acting as and which repository this directory resolves to. Call it when something 404s or 403s — the cause is almost always the wrong account, a missing token scope, or a directory that is not a GitHub checkout, not a bad query.

Tools

• github_status — signed-in account, scopes, and the repo this directory resolves to.
• github_search — issues, PRs, repos, code, or commits across GitHub, using GitHub search syntax.
• github_issue_list / github_issue_view — one repo's issues; the view includes the comment thread.
• github_pr_list / github_pr_view — pull requests; the view includes reviews and comments.
• github_pr_diff — the diff, or with namesOnly just the changed paths.
• github_pr_checks — CI check runs for a PR. A non-zero exit is the answer, not an error.
• github_run_list / github_run_view — Actions runs; failedLogs returns only the failing steps' output.
• github_api — any REST endpoint the named tools miss. GET only.
• github_cli — any other gh subcommand, as an argv array. This is the write path.

Every tool takes an optional repo as OWNER/REPO. Omit it to use the repository checked out in this session's project directory, exactly as running gh there would.