github

Automate GitHub operations using the gh CLI for issues, pull requests, and CI runs.

37|4|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/MerkyorLynn/Lynn --skill github-merkyorlynn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github
Source: https://github.com/MerkyorLynn/Lynn/tree/main/skills2set/github
Command: npx skills add https://github.com/MerkyorLynn/Lynn --skill github-merkyorlynn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes friction when you need to triage issues, review pull requests, and inspect CI results on GitHub without switching between web pages.

Core Features & Use Cases

  • Pull request CI inspection: Check PR checks and identify failed steps quickly.
  • Workflow run visibility: List recent runs, open a specific run, and view logs for failures.
  • Advanced GitHub queries via API: Fetch targeted fields using gh api when standard subcommands don’t cover your needs.
  • Structured outputs with JSON: Use --json and --jq to extract exactly the data you care about, such as issue numbers and titles.

Quick Start

Interact with a repository named owner/repo by running the GitHub CLI command you need, such as listing recent workflow runs for the last 10 executions.

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 and identify failed steps using gh cli?

Check pull request CI status by running gh cli commands to inspect PR checks and quickly identify failed workflow steps. You can view recent runs, open specific runs, and access logs to pinpoint exact failures without navigating web pages.

What is the best way to triage GitHub issues and pull requests in bulk?

Triage GitHub issues and pull requests in bulk by using gh cli commands with repository scoping via --repo owner/repo. You can apply structured output using --json and --jq to extract targeted fields like issue numbers and titles for advanced reporting.

How do I fetch specific repository fields when standard gh commands don't cover my needs?

Fetch specific repository fields by using gh api queries when standard subcommands don’t cover your needs. This allows targeted data lookups for advanced reporting, extracting exactly the data you care about with structured outputs via --json and --jq.

Does this GitHub workflow run inspection require any special dependencies or setup?

GitHub workflow run inspection requires no special dependencies, operating entirely through gh cli commands. You need gh pr, gh run, and gh api usage with repository scoping via --repo owner/repo to manage issues, PRs, and CI workflow runs.

Can I view workflow run logs for failures directly from the command line?

View workflow run logs for failures directly from the command line by listing recent runs, opening a specific run, and accessing logs. This removes friction when inspecting CI results without switching between web pages.

How do I list recent CI workflow runs for a specific repository?

List recent CI workflow runs for a specific repository by using gh run commands with repository scoping via --repo owner/repo. You can view the last 10 executions and open specific runs to investigate failed CI steps.