skills.rest
JOHNNYWHITEMIKE
JOHNNYWHITEMIKECOMMUNITY
Explore all skills by this author →
GitHub

github

Query and update GitHub repositories via the GitHub CLI.

Updated Apr 8, 2026
Search Tags:#code review#github#cli#pull requests#issue triage#gh api#ci runs
One-click install
npx skills add https://github.com/JOHNNYWHITEMIKE/openclaw --skill github-johnnywhitemike
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github
Source: https://github.com/JOHNNYWHITEMIKE/openclaw/tree/main/openclaw/.openclaw/openclaw/skills/github
Command: npx skills add https://github.com/JOHNNYWHITEMIKE/openclaw --skill github-johnnywhitemike

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It streamlines common GitHub workflows—like checking PR/CI status, triaging issues, and summarizing runs—so you do not have to switch to the web UI for routine operations.

Core Features & Use Cases

  • Pull request status & CI visibility: View PR details and workflow/run status, including failed-step logs, to quickly assess merge readiness.
  • Issue management: List, create, comment on, and close issues with consistent CLI commands.
  • GitHub API queries for structured data: Retrieve repository/PR/label data using gh api with --jq filtering for automation-friendly outputs.
  • Use Case: When a PR is opened, you can check its checks and review-relevant details (title, author, changed files, and run logs) and then decide whether to request changes or proceed with merge.

Quick Start

Use the GitHub skill to check whether pull request 55 for owner/repo has passing CI by running: gh pr checks 55 --repo owner/repo.

Frequently Asked Questions about github

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

FAQPage Schema
How do I check pull request CI status from the command line?▼

Check pull request CI status using the GitHub CLI to query workflow runs and view failed-step logs directly in your terminal. You can run a command like `gh pr checks 55` to assess merge readiness without opening the web UI.

What is the best way to triage GitHub issues without using the web interface?▼

Triage GitHub issues efficiently by using the GitHub CLI to list, create, comment on, and close issues with consistent commands. This streamlines routine repository management tasks directly from the terminal.

Do I need the gh binary and authentication to manage GitHub repositories via CLI?▼

Yes, you need the `gh` binary installed and GitHub authentication configured to manage repositories via CLI. This setup allows you to query and update repository state across issues, pull requests, and workflow runs.

Can I retrieve structured GitHub API data for automation using gh api?▼

Retrieve structured GitHub API data using `gh api` with `--jq` filtering for automation-friendly outputs. This allows you to extract deterministic repository, PR, and label data for automated workflows.

How do I view and merge pull requests from the command line?▼

View and merge pull requests from the command line by using GitHub CLI commands to check PR details like title, author, and changed files. You can evaluate this information alongside CI run logs to decide whether to proceed with the merge.

Why use GitHub CLI for issue triage instead of the web UI?▼

Using the GitHub CLI for issue triage prevents switching to the web UI for routine operations, streamlining workflows. It provides consistent commands to list, comment on, and close issues while keeping development context intact.

Related Skills

Explore More Product & Management Skills→
feiji77-2feiji77-2

GitHub

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

Community
Intermediate
bitan-delbitan-del
4

github

Automate GitHub repository management tasks using the gh CLI.

Community
Intermediate
starwardsstarwards
42

starwards-ci-debugging

Diagnose Starwards GitHub Actions CI failures from downloaded logs.

Official
Intermediate
rickypowellrickypowell
1

Using `gh` commands on the command line, bash, or zsh

Use GitHub CLI commands in bash or zsh with --body-file for multi-line text.

Community
Basic