Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
beita6969 avatar

Github

  • 19 installs
  • 869 repo stars
  • Updated June 8, 2026
  • beita6969/scienceclaw

github is a Claude skill that uses the gh CLI to manage GitHub issues, pull requests, CI runs, and API queries.

About

This skill uses the gh CLI to manage GitHub issues, pull requests, CI/workflow runs, and API queries. A developer uses it to check PR and CI status, create or comment on issues, merge PRs, and pull repository data. It excludes local git operations and non-GitHub hosts.

  • Drives GitHub issues, PRs, and CI runs via the gh CLI
  • Covers PR checks, merge, issue triage, and API queries
  • Includes JSON output with jq filtering templates

Github by the numbers

  • 19 all-time installs (skills.sh)
  • Ranked #388 of 735 Git & Pull Requests skills by installs in the Skillselion catalog
  • Data as of Aug 2, 2026 (Skillselion catalog sync)
At a glance

github capabilities & compatibility

Free; requires a configured gh auth login.

Capabilities
code review
Works with
github
Use cases
ci cd · project management
Platforms
macOS · Linux
Pricing
Free
From the docs

What github says it does

GitHub operations via `gh` CLI: issues, PRs, CI runs, code review, API queries.
SKILL.md
Local git operations (commit, push, pull, branch) → use `git` directly
SKILL.md
npx skills add https://github.com/beita6969/scienceclaw --skill github

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs19
repo stars869
Last updatedJune 8, 2026
Repositorybeita6969/scienceclaw

What it does

Manage GitHub issues, PRs, and CI runs from the terminal using the gh CLI.

Who is it for?

Checking PR/CI status, creating and triaging issues, merging PRs, and querying the GitHub API.

Skip if: Local git operations, non-GitHub hosts (GitLab/Bitbucket), or reviewing actual code diffs.

When should I use this skill?

You need to check PR/CI status, manage issues, or query GitHub data from the terminal.

What you get

  • PR and CI status
  • issue actions
  • GitHub API query results

By the numbers

  • 2 install methods (brew, apt)

Files

SKILL.mdMarkdownGitHub ↗

GitHub Skill

Use the gh CLI to interact with GitHub repositories, issues, PRs, and CI.

When to Use

USE this skill when:

  • Checking PR status, reviews, or merge readiness
  • Viewing CI/workflow run status and logs
  • Creating, closing, or commenting on issues
  • Creating or merging pull requests
  • Querying GitHub API for repository data
  • Listing repos, releases, or collaborators

When NOT to Use

DON'T use this skill when:

  • Local git operations (commit, push, pull, branch) → use git directly
  • Non-GitHub repos (GitLab, Bitbucket, self-hosted) → different CLIs
  • Cloning repositories → use git clone
  • Reviewing actual code changes → use coding-agent skill
  • Complex multi-file diffs → use coding-agent or read files directly

Setup

# Authenticate (one-time)
gh auth login

# Verify
gh auth status

Common Commands

Pull Requests

# List PRs
gh pr list --repo owner/repo

# Check CI status
gh pr checks 55 --repo owner/repo

# View PR details
gh pr view 55 --repo owner/repo

# Create PR
gh pr create --title "feat: add feature" --body "Description"

# Merge PR
gh pr merge 55 --squash --repo owner/repo

Issues

# List issues
gh issue list --repo owner/repo --state open

# Create issue
gh issue create --title "Bug: something broken" --body "Details..."

# Close issue
gh issue close 42 --repo owner/repo

CI/Workflow Runs

# List recent runs
gh run list --repo owner/repo --limit 10

# View specific run
gh run view <run-id> --repo owner/repo

# View failed step logs only
gh run view <run-id> --repo owner/repo --log-failed

# Re-run failed jobs
gh run rerun <run-id> --failed --repo owner/repo

API Queries

# Get PR with specific fields
gh api repos/owner/repo/pulls/55 --jq '.title, .state, .user.login'

# List all labels
gh api repos/owner/repo/labels --jq '.[].name'

# Get repo stats
gh api repos/owner/repo --jq '{stars: .stargazers_count, forks: .forks_count}'

JSON Output

Most commands support --json for structured output with --jq filtering:

gh issue list --repo owner/repo --json number,title --jq '.[] | "\(.number): \(.title)"'
gh pr list --json number,title,state,mergeable --jq '.[] | select(.mergeable == "MERGEABLE")'

Templates

PR Review Summary

# Get PR overview for review
PR=55 REPO=owner/repo
echo "## PR #$PR Summary"
gh pr view $PR --repo $REPO --json title,body,author,additions,deletions,changedFiles \
  --jq '"**\(.title)** by @\(.author.login)\n\n\(.body)\n\n📊 +\(.additions) -\(.deletions) across \(.changedFiles) files"'
gh pr checks $PR --repo $REPO

Issue Triage

# Quick issue triage view
gh issue list --repo owner/repo --state open --json number,title,labels,createdAt \
  --jq '.[] | "[\(.number)] \(.title) - \([.labels[].name] | join(", ")) (\(.createdAt[:10]))"'

Notes

  • Always specify --repo owner/repo when not in a git directory
  • Use URLs directly: gh pr view https://github.com/owner/repo/pull/55
  • Rate limits apply; use gh api --cache 1h for repeated queries

Related skills

FAQ

When should I not use this skill?

Not for local git operations (commit, push, branch), non-GitHub hosts like GitLab or Bitbucket, or reviewing actual code diffs.

Does it support structured output?

Yes, most commands support --json with --jq filtering for structured queries and templates.

Git & Pull Requestsgitintegrations

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.