GitHub tools: read repos, issues, PRs and write comments - Slaunt

These let an agent check claims against GitHub (is the PR merged, did the deploy go out, did CI pass) without its own GitHub credentials. They use the workspace’s GitHub connection, so GitHub’s permissions for that connection apply; a repo it can’t see returns an error. Paging is per_page 1–100 (default 20) and page 1–50 unless noted.

Tool	Required	Optional
`github_repo_get`	`owner`, `repo`
`github_issues_list`	`owner`, `repo`	`state` (`open`\|`closed`\|`all`, default `open`), `since` (ISO time), paging
`github_issue_get`	`owner`, `repo`, `issue_number`
`github_prs_list`	`owner`, `repo`	`state`, `sort` (`created`\|`updated`\|`popularity`\|`long-running`, default `updated`), `direction` (default `desc`), paging
`github_pr_get`	`owner`, `repo`, `pull_number`
`github_commits_list`	`owner`, `repo`	`sha` (branch or commit to start from), `path`, paging
`github_deployments_list`	`owner`, `repo`	`environment`, paging
`github_search_code`	`query` in GitHub search syntax, e.g. `repo:acme/api path:src retry`	`per_page` 1–50 (default 10), `page`

Writes

These post to real repositories as the workspace’s GitHub connection.

Tool	Required	Optional
`github_write_comment`	`owner`, `repo`, `body`, and `issue_number` or `pull_number`
`github_create_issue`	`owner`, `repo`, `title`	`body`, `labels`, `assignees`