Home Tutorials Categories Skills About
ZH EN JA KO
🐙

GitHub

Code Developer Tools

Install Command

npx clawhub@latest install github

Installation Guide

1
Check Environment

Make sure Node.js 22+ and OpenClaw are installed. Run openclaw --version in your terminal to verify.

2
Run Installation

Run the install command above in your terminal. ClawHub will automatically download and install GitHub to the ~/.openclaw/skills/ directory.

3
Verify Installation

Run openclaw skills list to check your installed skills and confirm GitHub appears in the list.

4
Configure (Optional)

Follow the configuration instructions in the description below to add skill settings to ~/.config/openclaw/openclaw.json5.

Manual Installation: Copy the Skill folder to ~/.openclaw/skills/ or the skills/ directory in your project root. Make sure the folder contains a SKILL.md file.
Repo Management Issue/PR Actions

Detailed Description

The GitHub skill is one of the most beloved OpenClaw extensions for developers, letting you manage code repositories, Issues, Pull Requests, and more on GitHub using natural language.

Core Features

  • Repository Management: List, create, and search repositories; view repository info and file contents
  • Issue Operations: Create Issues, add comments, change status and labels, search Issues
  • PR Management: View PR details and diffs, review PRs, merge PRs
  • Code Search: Search code snippets within a repository or across all of GitHub
  • Actions Monitoring: View CI/CD workflow status and re-run failed workflows
  • Release Management: Create and manage releases

Configuration

Requires a GitHub Personal Access Token (PAT).

{
  skills: {
    github: {
      token: "ghp_xxxxxxxxxxxx",
      defaultOwner: "your-username",
      notifyOnPR: true
    }
  }
}

Use Cases

  • "Show me the unmerged PRs on the main branch recently"
  • "Create an Issue titled Bug: Login page error"
  • "How do the changes in this PR look? Any potential issues?"
  • "Have any recent CI runs failed? What was the cause?"

Security Recommendations

It is recommended to create a Token with minimal permissions, granting access only to the necessary repositories and operations. Avoid using a global Token with admin privileges.