aj-github

What This Skill Does

The aj-github skill acts as a robust interface for the GitHub ecosystem by wrapping the powerful gh CLI. It enables OpenClaw agents to manage the full lifecycle of software development without leaving the environment. Whether you need to audit pull requests, investigate CI/CD failures, or query complex repository data via the GitHub API, this skill provides the necessary command-line leverage to execute these tasks precisely.

Installation

To integrate this skill into your OpenClaw agent, execute the following command in your terminal: clawhub install openclaw/skills/skills/aceundefeated/aj-github Ensure that your environment has the gh CLI installed and authenticated before attempting to use the skill.

Use Cases

This skill is indispensable for DevOps engineers, software developers, and QA automation specialists. Primary use cases include:

• Automated CI/CD troubleshooting: Automatically pulling logs from failed workflow runs.
• PR management: Listing, checking status, and filtering pull requests across multiple repositories.
• Advanced Data Retrieval: Fetching specific metadata from repository objects that are not easily accessible via standard web UIs.
• Batch operations: Processing multiple issues or PRs simultaneously using structured JSON output and filtering.

Example Prompts

1. "Check the status of all current pull requests in the openclaw/skills repository and identify which ones have failed CI checks."
2. "Find the most recent workflow run for the main branch, retrieve the log file for any failed steps, and summarize the error message for me."
3. "List the top 5 open issues in the repository assigned to me, including their titles and creation dates, formatted as a simple list."

Tips & Limitations

• Always include the --repo owner/repo flag if you are not running the agent within a git-initialized directory, as the skill needs explicit context to function.
• Leverage the --json and --jq flags whenever possible. This transforms raw command output into clean, parsable data that your AI agent can better understand and act upon.
• Be mindful of GitHub API rate limits. While gh handles most authentication seamlessly, very high-frequency automated queries might trigger rate limiting on large repositories.
• If a specific command is not supported by standard gh subcommands, use gh api to access any endpoint in the GitHub REST API.