Github
Interact with GitHub using the gh CLI. Use gh issue, gh pr, gh run, and gh api for repository management.
Details
GitHub integration for managing repositories, issues, and pull requests. Interact with GitHub using the gh CLI: gh issue, gh pr, gh run, and gh api. Essential for developers and version-controlled workflows.
When to use
Use when the agent should create or manage issues, PRs, runs, or call GitHub API. Requires gh auth; ideal for triage, release notes, and CI-related automation.
Repository chores, delegated
The GitHub skill connects your assistant to the gh CLI — issues, pull requests, workflow runs, and the full API surface beneath them. That turns a large class of development housekeeping into chat messages: triage this issue, check why the run failed, draft release notes from what merged this week. With over 10,000 downloads, it is the standard way OpenClaw setups participate in version-controlled work.
The shape of the value is worth noticing: none of these tasks are difficult, they are just constant, and they interrupt deeper work. An assistant that handles them in the team channel — where the discussion already lives — removes a steady tax on attention rather than any single big burden.
Triage, release notes, and CI
Three patterns dominate real-world use. Issue and PR triage: labelling, assigning, summarising, and chasing the stale ones. Release documentation: turning a week of merged PRs into notes a human would willingly read. And CI awareness: watching runs through gh run, reporting failures with context, and saving you the tab-switch to find out why the build went red.
Installing the GitHub skill
Run the command below from your OpenClaw directory and restart the assistant. The prerequisite that matters is gh auth — the skill works through the authenticated GitHub CLI, so complete that login before the first request. Scope the token to what the assistant should actually touch.
clawhub install githubPart of a development stack
GitHub integration rarely works alone. In practice it sits alongside shell access for running what gets discussed and context tools for understanding the codebase the issues refer to — a stack where each piece makes the others more useful. Assembling that stack coherently, with sensible permissions at every layer, is precisely what we do when we set up OpenClaw for engineering teams.