Github
Drive GitHub issues, PRs, CI checks, reviews, releases, and API queries from your agent via the official `gh` CLI instead of brittle browser scraping.
Overview
GitHub is an agent skill most often used in Build (also Ship review workflows) that runs GitHub issues, PRs, CI logs, reviews, releases, and `gh api` through the GitHub CLI.
Install
npx skills add https://github.com/steipete/clawdis --skill githubWhat is this skill?
- Covers PR list/view/diff/checks/create/merge, issues, and `gh api` patterns in one skill
- Documents auth (`gh auth status/login`) and `GH_CONFIG_DIR` when gateway HOME differs from operator HOME
- Explicit split: use `gh` for GitHub remote ops; use `git` for local branch/commit/push
- Supports direct PR URLs and `--json` fields for agent-friendly structured output
- Install paths via Homebrew or apt for the `gh` binary (metadata requires bins: gh)
- Requires `gh` binary with brew or apt install options in skill metadata
Adoption & trust: 2k installs on skills.sh; 378k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You need your agent to act on real GitHub PRs, checks, and issues but only know ad-hoc `git` commands or fragile web UI steps.
Who is it for?
Solo builders who already use GitHub for shipping and want the agent to list PRs, read check failures, and draft or merge PRs via `gh`.
Skip if: Deep line-by-line code review in the repo—that belongs on code-reading/review skills; skip if you do not use GitHub or cannot install `gh`.
When should I use this skill?
You need GitHub-hosted operations (PRs, issues, checks, releases, `gh api`) and `gh` is or can be installed.
What do I get? / Deliverables
Your agent issues structured `gh` commands for auth, PR/issue lifecycle, and API queries so you can merge, debug CI, and comment without manual GitHub UI hopping.
- Executable `gh` command sequences for PR/issue/release actions
- Structured JSON snapshots from `gh … --json` for agent reasoning
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Canonical shelf is Build → integrations because the skill wires the agent to GitHub’s hosted workflow (PRs, checks, issues) while local git stays separate. Subphase integrations fits third-party CLI bridges (`gh`) that extend the repo toolchain beyond plain `git` commits.
Where it fits
Agent opens a feature PR and attaches check status JSON before you hand off to human review.
You ask the agent to pull `gh pr diff` and failed `gh pr checks` after a red CI run.
Agent lists open issues and drafts comment-ready summaries from `gh issue list`.
How it compares
Use this as the hosted-GitHub CLI playbook, not as a replacement for local `git` or static code-audit skills.
Common Questions / FAQ
Who is github for?
Solo and indie developers shipping on GitHub who want their coding agent to manage PRs, issues, CI status, and releases through the official CLI.
When should I use github?
During build when wiring agent workflows to your repo; during ship when checking PR checks, reviews, and merge readiness; and during operate when triaging issues or pulling CI logs from production repos.
Is github safe to install?
It documents standard `gh` auth and repo-scoped commands; review the Security Audits panel on this Prism page and treat API tokens and repo access like any production credential.
SKILL.md
READMESKILL.md - Github
# GitHub Use `gh` for GitHub. Use `git` for local commits/branches/push/pull. Use code-reading tools for deep reviews. ## Auth ```bash gh auth status gh auth login ``` Gateway HOME can differ from operator HOME. If `gh` auth exists elsewhere, set `GH_CONFIG_DIR` in the gateway service env and restart. ## PRs ```bash gh pr list --repo owner/repo --json number,title,state,author,url gh pr view 55 --repo owner/repo --json title,body,author,files,commits,reviews,reviewDecision gh pr checks 55 --repo owner/repo gh pr diff 55 --repo owner/repo gh pr create --repo owner/repo --title "feat: title" --body-file /tmp/pr.md gh pr merge 55 --repo owner/repo --squash ``` URLs work directly: `gh pr view https://github.com/owner/repo/pull/55`. ## Issues ```bash gh issue list --repo owner/repo --state open --json number,title,labels,url gh issue view 42 --repo owner/repo --json title,body,comments,labels,state gh issue create --repo owner/repo --title "Bug: ..." --body-file /tmp/issue.md gh issue comment 42 --repo owner/repo --body-file /tmp/comment.md gh issue close 42 --repo owner/repo --comment "Fixed in ..." ``` ## CI/runs ```bash gh run list --repo owner/repo --limit 10 gh run view <run-id> --repo owner/repo --json status,conclusion,headSha,url gh run view <run-id> --repo owner/repo --log-failed gh run rerun <run-id> --repo owner/repo --failed ``` ## API ```bash gh api repos/owner/repo/pulls/55 --jq '.title, .state, .user.login' gh api repos/owner/repo/labels --jq '.[].name' gh api --cache 1h repos/owner/repo --jq '{stars: .stargazers_count, forks: .forks_count}' ``` Use `--json` + `--jq` for structured output. Use `--body-file` for comments/bodies containing backticks, shell snippets, env names, or user text.