github

What This Skill Does

The GitHub skill enables your OpenClaw agent to interact directly with GitHub repositories using the powerful gh Command Line Interface. It serves as a bridge between your agent and the GitHub platform, allowing for automated issue tracking, pull request management, CI/CD pipeline monitoring, and advanced data extraction via the GitHub API. By leveraging the gh tool, the agent can perform complex administrative tasks, fetch logs from failed workflow runs, and parse JSON-formatted data directly from the GitHub servers, significantly reducing the manual overhead for developers and DevOps engineers.

Installation

To integrate this skill into your environment, run the following command in your terminal:

clawhub install openclaw/skills/skills/bobdevibecoder/bobagent-github

Ensure that the gh CLI is installed and configured on your machine before running this command, as the agent requires local access to authentication tokens stored by GitHub.

Use Cases

• DevOps Monitoring: Automatically monitor CI/CD pipeline health and alert team members when critical build steps fail.
• PR Triage: Bulk-list open pull requests and filter them by specific criteria to manage code review queues effectively.
• Automated Reporting: Generate custom reports using the gh api command to extract specific repository data (e.g., contributor activity, issue labels, or milestone progress) in structured formats.
• Troubleshooting: Rapidly fetch logs from failing workflows to identify the root cause without switching context from the command line.

Example Prompts

1. "Check the current status of all open pull requests in the openclaw/skills repository and list their titles."
2. "Show me the last 5 workflow runs for the repo openclaw/skills and let me know if any of them failed."
3. "Fetch the details for issue #55 on the repository, specifically looking for the current state and the user who opened it."

Tips & Limitations

• Always specify the repo: Unless you are inside a directory that is already a git clone of the target repo, you must explicitly use the --repo owner/repo flag.
• Data Formatting: Utilize the --json and --jq flags whenever possible to allow the agent to process output more accurately. Raw text output can be harder for the agent to parse than structured JSON.
• Authentication: The skill relies on your existing gh CLI authentication. If your token expires, the agent will report authorization errors; ensure your session is active by running gh auth status manually if issues persist.
• Permissions: The agent operates under your personal GitHub permissions. Be mindful that any command the agent executes (such as closing an issue) will be attributed to your GitHub account.