github

Manage GitHub issues, pull requests, and CI runs via the gh CLI.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/srgaba/open-claw --skill github-srgaba
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github
Source: https://github.com/srgaba/open-claw/tree/main/project/skills/github
Command: npx skills add https://github.com/srgaba/open-claw --skill github-srgaba

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Interacting with GitHub through the web UI is slow and hard to automate. This Skill lets you perform common GitHub operations—checking PR status, triaging issues, inspecting CI runs, and querying the API—directly from the command line using the official gh CLI. ## Core Features & Use Cases - Pull Request Management: List, view, create, merge PRs, and check CI status with gh pr commands. - Issue Operations: Create, list, close, and triage issues with structured JSON output and --jq filtering. - CI/Workflow Inspection: View workflow runs, fetch failed step logs, and re-run failed jobs. - API Queries: Run arbitrary GitHub API queries via gh api with jq-based field extraction. - Use Case: Before merging a feature branch, run gh pr checks 55 --repo owner/repo to verify CI passed, then generate a review summary showing the author, diff stats, and changed files. ## Quick Start Ask the assistant to check the CI status and review summary of pull request number 55 in your repository using the gh CLI.

Frequently Asked Questions about github

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check PR status and CI checks from the command line?

Use gh pr checks followed by the PR number and repository, such as gh pr checks 55 --repo owner/repo. For full PR details including author and diff stats, run gh pr view with the --json flag and filter fields using --jq.

How do I view failed GitHub Actions workflow logs?

Run gh run view with the run ID and the --log-failed flag to show only failed step logs. You can list recent runs first with gh run list --repo owner/repo --limit 10, then re-run failures using gh run rerun <run-id> --failed.

Does the gh CLI work with GitLab or Bitbucket repositories?

No, the gh CLI only works with GitHub repositories, including GitHub Enterprise when configured. For GitLab, Bitbucket, or self-hosted alternatives, you need their respective CLIs or APIs instead.

Why does gh fail with authentication errors?

The gh CLI requires one-time authentication via gh auth login before use. Verify your session with gh auth status; if it fails, re-authenticate and ensure the token has the required repository scopes.

When should I use git directly instead of the gh CLI?

Use git directly for local operations like commit, push, pull, branching, and cloning repositories. The gh CLI is designed for GitHub platform operations such as PRs, issues, releases, and API queries, not local version control.