github

Automate GitHub repository management with the gh CLI for PRs, issues, and CI runs.

6|1|Updated Feb 23, 2026
One-click install
npx skills add https://github.com/flemzord/sclaw --skill github-flemzord
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github
Source: https://github.com/flemzord/sclaw/tree/main/skills/github
Command: npx skills add https://github.com/flemzord/sclaw --skill github-flemzord

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines GitHub repository management by harnessing the gh CLI to perform routine tasks such as managing PRs, issues, and CI checks, reducing manual effort and context switching.

Core Features & Use Cases

  • PR and issue management: list, view, create, and comment on PRs and issues across repositories.
  • CI and workflow visibility: monitor workflow runs and job statuses.
  • API queries and automation: fetch repository data and automate common maintainer tasks.

Quick Start

Query open PRs and their statuses for a repository to get started.

Frequently Asked Questions about github

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

FAQPage Schema
How do I automate GitHub pull request and issue management across multiple repositories?

You can automate GitHub pull request and issue management by using the gh CLI to list, view, create, and comment on PRs and issues across multiple repositories with sensible defaults.

How do I check CI workflow run and job statuses using the gh CLI?

Checking CI workflow run and job statuses via the gh CLI provides direct visibility into your GitHub Actions workflows, allowing you to monitor continuous integration checks without manual context switching.

Do I need to authenticate the gh CLI before querying repository data and automating maintainer tasks?

Yes, querying repository data and automating maintainer tasks requires the gh binary to be installed and authenticated, ensuring secure access to your GitHub workflows.

What safeguards exist when automating GitHub repository management to prevent destructive operations?

Automating GitHub repository management includes safeguards and sensible defaults to prevent destructive operations, ensuring that routine PR, issue, and CI tasks execute safely without unintended side effects.

Can I fetch repository data and automate common maintainer tasks without switching contexts?

Fetching repository data and automating common maintainer tasks without context switching is possible by harnessing the gh CLI, streamlining your workflow directly from your current environment.