The most time-consuming part of dev collaboration is not writing code — it is running the GitHub flow. Checking issues, opening PRs, watching CI, cutting releases: every step costs multiple browser clicks. OpenClaw's official GitHub Skill pulls all of it into the command line with gh: issues, PRs, CI logs, comments, reviews, releases, repos — one command at a time.
Division of labor: GitHub goes to gh, local goes to git
The skill draws a clean line: GitHub-side operations (remotes, PRs, issues, CI, releases) use gh; local version control (commit, branch, push/pull) uses git; deep code review uses code-reading tools. Three tools, each in its lane.
Core capabilities
Auth management:
gh auth statuschecks login state,gh auth loginsigns inIssues & PRs: create, list, view, comment on, and close issues and PRs; handle review comments
CI logs: pull workflow/check run logs and pinpoint the failing step
Release management: create and publish releases, manage tags
gh api: hit any GitHub REST/GraphQL endpoint directly — no ceiling on custom queries
Typical use cases
Daily dev flow: issue → PR → CI → merge, all from the terminal without switching to a browser
CI failure triage: a PR is red — pull the CI log and see exactly which step and assertion failed
Automation integration: agents drive GitHub directly (open issues, reply to reviews, cut releases), closing the loop with gh-issues
How to use & download
OpenClaw users: github is a built-in skill — install the gh CLI first (brew or apt); trigger everyday GitHub work in natural language. See GitHub CLI site and OpenClaw docs.
Other agent users: gh is a standalone open-source CLI, callable by any script or agent. Source: GitHub CLI repo.
Related resources
GitHub skills work together: issue-fixing flow (gh-issues) auto-picks issues and spawns fix agents to open PRs; flaky CI pairs with Node.js debugging (node-inspect-debugger) or Python debugging (python-debugpy).