github-tools

What This Skill Does

The github-tools skill integrates the powerful GitHub CLI (gh) directly into your OpenClaw agent, enabling seamless automation of GitHub workflows. Instead of manually navigating the web interface, the agent can programmatically manage pull requests, investigate CI/CD failures, track issues, and execute complex API queries. By leveraging the underlying gh CLI, this skill ensures that all interactions are authenticated and follow standard GitHub best practices. It is designed to act as a bridge between your local environment or server and your remote GitHub repositories.

Installation

To install this skill, run the following command in your terminal: clawhub install openclaw/skills/skills/164149043/github-tools Ensure you have the gh CLI installed on your machine and that you have successfully authenticated using gh auth login before triggering the skill for the first time.

Use Cases

This skill is ideal for developers and DevOps engineers who want to automate repetitive tasks. Common use cases include:

• CI/CD Debugging: Automatically identify failed workflow runs and extract logs for specific steps when a build breaks.
• PR Triage: Bulk processing or querying of PR metadata to identify stalled tasks or pending reviews.
• Automated Reporting: Creating formatted lists of issues or PRs using the JSON output feature to integrate with other reporting tools.
• Advanced Data Retrieval: Querying the GitHub API for custom data points that are not exposed via standard CLI commands by using gh api with specific JQ filters.

Example Prompts

1. "Check the status of the CI checks for PR #55 in the openclaw/core repository and tell me if any steps failed."
2. "List the last 5 workflow runs for our main repository and provide a summary of their status."
3. "Fetch the title and author of all open issues in the current repo, formatted as a simple numbered list."

Tips & Limitations

• Permissions: Ensure the token used for gh has the necessary scopes (repo, read:org, etc.) for the tasks you wish to perform.
• Targeting Repos: Always use the --repo owner/repo flag unless you are currently inside a initialized git directory that points to the target repository.
• Performance: For large datasets, utilize the --jq flag to filter data on the server side rather than pulling large JSON blobs into the agent memory.
• Rate Limiting: Be aware of GitHub API rate limits when running automated scripts that query many resources at once.