github

Manage GitHub repositories, pull requests, issues, and workflow runs via the gh CLI.

Updated Mar 13, 2026
One-click install
npx skills add https://github.com/Yogi-076/Vajrascan.on --skill github-yogi-076
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github
Source: https://github.com/Yogi-076/Vajrascan.on/tree/main/moltbot/skills/github
Command: npx skills add https://github.com/Yogi-076/Vajrascan.on --skill github-yogi-076

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a concise, CLI-driven way to inspect and manage GitHub repositories, pull requests, issues, and workflow runs without navigating the web UI, speeding up triage and CI debugging.

Core Features & Use Cases

  • Quick CI Inspection: Check pull request check status and view failing workflow steps to identify CI issues faster.
  • Workflow and Run Management: List recent workflow runs and view logs for specific runs to diagnose broken pipelines.
  • Advanced Queries: Use the GitHub API via CLI to fetch specific fields from PRs or issues for automation and reporting.
  • Use Case: A developer verifying why a PR's CI failed can list runs, view the failing steps log, and fetch PR metadata for a comment or automation.

Quick Start

Use the gh CLI to check CI status for pull request 55 in owner/repo, specifying --repo owner/repo if not inside the repository.

Frequently Asked Questions about github

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

FAQPage Schema
How do I check the CI status of a pull request using the GitHub CLI?

Check pull request CI status by running the GitHub CLI to view check statuses and identify failing workflow steps. Specify --repo owner/repo if you are not inside the repository directory to ensure accurate results.

How do I view logs for a specific GitHub Actions workflow run from the command line?

View workflow run logs by listing recent runs with the gh CLI, then requesting the logs for the specific failing run. This allows you to diagnose broken pipelines and identify failing steps directly in your terminal.

Can I fetch specific fields from GitHub issues and PRs for automation without the web UI?

Fetch specific fields from issues and PRs by using the GitHub API via the gh CLI. This enables automation and reporting tasks by retrieving precise metadata needed for scripts or automated comments.

Do I need the GitHub CLI installed in PATH to manage repositories and triage issues?

The GitHub CLI must be available in PATH to manage repositories, triage issues, and inspect workflow runs. Using --repo owner/repo is recommended when operating outside a local git directory.

What is the best way to troubleshoot failing CI pipelines for GitHub repositories?

Troubleshoot failing CI pipelines by using the gh CLI to list recent workflow runs, view the logs for the failing run, and inspect pull request check statuses. This accelerates debugging without navigating the web UI.

Why does running a gh CLI command outside a git directory fail to find my repository?

Running gh CLI commands outside a git directory fails because the tool lacks repository context. Provide the --repo owner/repo flag with your command to specify the target repository explicitly.