github

Manage GitHub PRs, issues, and CI workflows via the gh CLI.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/Jnuso/OpenClaw --skill github-jnuso
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github
Source: https://github.com/Jnuso/OpenClaw/tree/main/skills/github
Command: npx skills add https://github.com/Jnuso/OpenClaw --skill github-jnuso

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GitHub operations are often repetitive, error-prone, and time-consuming when performed via the web UI. This skill enables quick, scriptable interactions using the gh CLI, reducing manual context switching.

Core Features & Use Cases

  • Manage pull requests: list, view, create, merge, and comment on PRs.
  • Handle issues: list, create, close, and comment on issues.
  • Monitor CI/workflows: view run statuses and logs, trigger actions when supported.

Quick Start

Authenticate with gh auth login, then start managing PRs, issues, and CI checks with gh pr and gh issue commands.

Frequently Asked Questions about github

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

FAQPage Schema
How do I manage GitHub pull requests and issues from the command line?

You can manage GitHub pull requests and issues by executing gh CLI subcommands to list, view, create, merge, and comment on them. This streamlines code reviews and issue triage without manual web UI context switching.

What is the best way to monitor GitHub CI workflows remotely?

Monitoring GitHub CI workflows is handled by running gh CLI commands to view run statuses and fetch logs. You can check pipeline progress and trigger supported actions directly across multiple repositories.

Do I need to authenticate before using gh CLI to manage repository resources?

Yes, authenticating with gh auth login is required before managing repository resources. You must have repository access and execute gh subcommands to fetch or modify pull requests, issues, and CI data.

Can I automate GitHub operations across multiple repositories simultaneously?

Yes, you can apply gh CLI interactions across multiple repositories to streamline code reviews, issue triage, and pipeline monitoring. This scriptable approach reduces repetitive manual operations via the web UI.

Why use gh CLI instead of the GitHub web UI for pull requests and issue triage?

Using the gh CLI instead of the GitHub web UI reduces manual context switching and handles repetitive operations more quickly. It provides scriptable interactions for pull requests, issues, and CI workflows.

What are the limitations of managing GitHub workflows via gh CLI?

Limitations include requiring prior authentication and direct repository access to execute subcommands. Additionally, triggering GitHub Actions is only supported when explicitly allowed, restricting automated pipeline modifications.