Automate GitHub Workflows with the GitHub Skill: PRs, Issues, and CI from the Command Line

If you've ever found yourself jumping between browser tabs to check CI status, review pull requests, or manage issues, the GitHub skill for ClawdHub is about to become your new best friend. This skill brings the full power of GitHub's gh CLI directly into your Clawdbot workflows, letting your AI agent interact with repositories, track CI runs, and query data without leaving your terminal.

Who Needs This?

The GitHub skill is perfect for:

• Developers who want their AI assistant to check PR status, view failed CI logs, or list recent issues
• DevOps engineers monitoring workflow runs across multiple repositories
• Open source maintainers who need quick access to issue triage and PR management
• Anyone who's tired of context-switching to the GitHub web interface

Installation

Getting started is simple. First, install the skill:

npx clawhub@latest install github

The skill requires the GitHub CLI (gh) to be installed and authenticated. If you haven't set that up yet:

# Install gh CLI (macOS)
brew install gh

# Or on Linux
sudo apt install gh

# Authenticate with your GitHub account
gh auth login

Follow the interactive prompts to authenticate via browser or token. Once authenticated, you're ready to go.

Key Features

Pull Request Management

Check CI status on any pull request:

gh pr checks 55 --repo owner/repo

This gives you a quick overview of all status checks—no browser needed.

CI/CD Workflow Monitoring

List recent workflow runs:

gh run list --repo owner/repo --limit 10

View details of a specific run:

gh run view <run-id> --repo owner/repo

When something fails (and it always does eventually), get straight to the logs:

gh run view <run-id> --repo owner/repo --log-failed

This shows only the failed steps—cutting through the noise to find what actually broke.

Advanced API Queries

The gh api command unlocks access to anything in the GitHub API:

gh api repos/owner/repo/pulls/55 --jq '.title, .state, .user.login'

Need structured data? Most commands support JSON output with jq filtering:

gh issue list --repo owner/repo --json number,title --jq '.[] | "\(.number): \(.title)"'

Practical Examples

Ask your agent: "Check if my PR #42 passed CI in the clawdbot/clawdbot repo"

Agent runs: gh pr checks 42 --repo clawdbot/clawdbot

Ask: "Show me the failed steps from the last CI run"

Agent runs: gh run list --repo owner/repo --limit 1 then gh run view <id> --log-failed

Ask: "List open issues labeled 'bug' in my project"

Agent runs: gh issue list --repo owner/repo --label bug --state open

Pro Tips

1. Always specify --repo owner/repo when not in a git directory—the skill works anywhere, but needs to know which repo to target.

2. Use --json for scripting—structured output is easier for agents to parse and reason about.

3. The --jq flag is powerful—combine it with JSON output to extract exactly what you need without extra processing.

4. Check multiple PRs at once by scripting: for pr in 50 51 52; do gh pr checks $pr --repo owner/repo; done

5. Set default repo in your git directory with gh repo set-default to skip the --repo flag.

Security Note

This skill is rated Benign with high confidence. It's instruction-only—no extra environment variables, installs, or privileges required beyond the standard gh CLI authentication you've already set up.

Conclusion

The GitHub skill transforms your AI agent into a powerful GitHub command center. Whether you're debugging failed CI, triaging issues, or reviewing PRs, everything happens through natural conversation. No more browser tabs, no more context switching.

With 19.6k downloads and 52 stars, it's one of the most popular skills on ClawdHub for good reason. Install it today and let your agent handle the GitHub grunt work.

Links:

• GitHub Skill on ClawHub
• gh CLI Documentation
• ClawdHub Skills Directory