github

Automate GitHub workflows and repository management using the gh CLI.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/buer2233/my_openclaw --skill github-buer2233
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github
Source: https://github.com/buer2233/my_openclaw/tree/main/skills/github
Command: npx skills add https://github.com/buer2233/my_openclaw --skill github-buer2233

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GitHub tasks are often repetitive when done from a shell; this Skill enables direct, scriptable interaction with GitHub through the gh CLI to manage issues, PRs, and CI workflows.

Core Features & Use Cases

  • Create, list, and manage issues and pull requests using gh commands.
  • Check CI status, view workflow runs, and fetch data with gh run and gh api.
  • Use gh in automation scripts to implement repeatable GitHub operations.

Quick Start

Authenticate with gh and run a simple command to verify connectivity.

Frequently Asked Questions about github

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

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

You can automate GitHub issues and pull requests from the command line by executing scriptable gh CLI commands to create, list, and manage repository items directly.

Can I check CI workflow run status across multiple repositories using gh?

Yes, you can check CI workflow run status across multiple repositories using gh run and gh api commands, scoping queries with --repo owner/repo or direct URLs when not in a git directory.

Do I need to authenticate the gh CLI before managing pull requests?

Yes, you need to authenticate the gh CLI before managing pull requests; the Skill requires gh to be installed and authenticated to execute scriptable GitHub workflows and repository management tasks.

What is the best way to script repeatable GitHub operations for CI runs?

The best way to script repeatable GitHub operations for CI runs is using gh CLI commands within automation scripts to monitor workflows and fetch data with gh run and gh api.

How do I scope gh commands when I am not inside a git directory?

You scope gh commands when not inside a git directory by appending --repo owner/repo or using direct URLs, ensuring the command targets the correct repository for issues or PRs.

Why use the gh CLI instead of the GitHub API directly for repository management?

Use the gh CLI instead of the GitHub API directly for repository management because it provides scriptable shell interaction, simplifying repetitive issues, PRs, and CI workflows without manual API queries.