GitHub

OpenClaw contributorsIntegrationsOpenClaw

Inspect issues, pull requests and CI checks with OpenClaw’s GitHub CLI skill.

View source

Illustrative GitHub workflow: Repository + PR URL; example output includes Changed files, Check failures, Review next steps.

Set up GitHub

This skill ships with OpenClaw. Inspect its setup and check the required tools in the runtime where OpenClaw runs.

Inspect the bundled skill

openclaw skills info github

Check runtime requirements

openclaw skills check

These commands inspect skill availability; they do not install dependencies or connect accounts. Follow the source’s setup requirements in your own environment.

What this skill helps with

The GitHub skill in OpenClaw’s repository guides use of the gh CLI for issues, pull requests, check logs, reviews, releases and API queries. It distinguishes GitHub operations from local Git branch and commit work.

When to use it

Use it to inspect a pull request, find failing CI jobs, review an issue or query repository metadata. For deep code review, combine the GitHub context with actual code-reading tools.

What to bring

Provide a repository URL or owner/repository identifier and the issue, PR or run you want to inspect. The runtime needs gh on its PATH and authentication with access to that repository.

What to expect

Expect source-linked issue or PR details, CI findings or a specific repository action within your permissions. The review summary illustrated here is fictional; this page does not access your repositories.

How the skill works

Establish repository context

Confirm the target repository and verify that the GitHub CLI is available and authenticated in the environment used by OpenClaw.

Read the relevant evidence

Use PR, issue and check commands for the task. Structured JSON and filtered API reads can keep the response focused.

Verify the requested outcome

For write actions, confirm the authorised scope and re-read the resulting GitHub state. A completed review alone does not prove a pull request was merged.

GitHub skill questions

What dependency does it require?

The published metadata requires the gh binary. Repository access also depends on the account authenticated in the OpenClaw runtime.

Is it a local Git replacement?

No. The source uses gh for GitHub and git for local commits, branches, pushes and pulls.

Find the next skill for your workflow

Explore more task-specific skills, compare their requirements and review their original sources.

Browse Agent Skills