github

Automate GitHub tasks by driving the gh CLI for issues, PRs, CI, and API queries.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GitHub project maintenance and data retrieval often require switching between the web UI and the terminal. This skill enables executing common GitHub tasks from the command line using the gh CLI, saving time and reducing context switching.

Core Features & Use Cases

  • Integrated gh issue management: list, create, or comment on issues across repositories.
  • Pull request workflows: list, view, and manage PRs, including status checks and merges.
  • CI and API queries: inspect workflow runs and fetch data via gh api for advanced insights.
  • Use case: a maintainer quickly audits open PRs across multiple repos and retrieves their statuses for reporting.

Quick Start

Ask the AI to list open pull requests in a given repo using gh.

Frequently Asked Questions about github

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

FAQPage Schema
How do I automate GitHub issue management from the command line?

You can automate GitHub issue management by driving the gh CLI to list, create, or comment on issues across repositories without switching to the web UI. This skill executes these actions directly from your terminal using explicit --repo inputs.

Can I check CI workflow status for multiple repositories using gh CLI?

Yes, you can check CI workflow status across multiple repositories using the gh CLI. This skill inspects workflow runs and fetches data via gh api, allowing maintainers to audit PR statuses and CI checks for reporting.

Do I need to install gh CLI to manage pull requests with this automation approach?

Yes, installing and configuring the gh CLI is required to manage pull requests with this automation approach. The skill drives the gh CLI to list, view, and merge PRs, requiring it to be configured with access to the target repository.

What is the best way to fetch GitHub API data for advanced repository insights?

The best way to fetch GitHub API data for advanced repository insights is by executing gh api queries through this skill. It automates data retrieval directly from the terminal, fetching advanced insights without leaving the command line environment.

Why does the gh CLI require explicit --repo inputs when not in a git directory?

The gh CLI requires explicit --repo inputs when not in a git directory because it lacks local context to identify the target repository. Providing the --repo flag ensures the commands execute actions against the correct remote repository URL.