Index of every page on this site: llms.txt
All skills
dimillian avatar

/github

@05ba982 official
by Thomas Ricouarddimillian/skills4k stars
208
Run it yourself

Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries. Use when the user asks about GitHub issues, pull requests, workflows, or wants to interact with GitHub repositories from the command line — including tasks like check CI status, create PR, list issues, or query the GitHub API.

Use this Skill: https://skilld.dev/gh/dimillian/skills/github

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈93 tokens for metadata: the name and description. ≈381 when used: this file. ≈48 more on demand in 1 file.

Description uses 4.7% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈372 characters, or 4.7%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

GitHub Skill

Use the gh CLI to interact with GitHub. Always specify --repo owner/repo when not in a git directory, or use URLs directly.

Pull Requests

Check CI status on a PR:

gh pr checks 55 --repo owner/repo

List recent workflow runs:

gh run list --repo owner/repo --limit 10

View a run and see which steps failed:

gh run view <run-id> --repo owner/repo

View logs for failed steps only:

gh run view <run-id> --repo owner/repo --log-failed

Debugging a CI Failure

Follow this sequence to investigate a failing CI run:

  1. Check PR status — identify which checks are failing:
    gh pr checks 55 --repo owner/repo
  2. List recent runs — find the relevant run ID:
    gh run list --repo owner/repo --limit 10
  3. View the failed run — see which jobs and steps failed:
    gh run view <run-id> --repo owner/repo
  4. Fetch failure logs — get the detailed output for failed steps:
    gh run view <run-id> --repo owner/repo --log-failed

API for Advanced Queries

The gh api command is useful for accessing data not available through other subcommands.

Get PR with specific fields:

gh api repos/owner/repo/pulls/55 --jq '.title, .state, .user.login'

JSON Output

Most commands support --json for structured output. You can use --jq to filter:

gh issue list --repo owner/repo --json number,title --jq '.[] | "\(.number): \(.title)"'

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning2mo5 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    The skill facilitates interaction with GitHub repositories using the gh CLI. While it contains no inherently malicious code, it is susceptible to indirect prompt injection because it ingests untrusted data from GitHub—such as pull request descriptions, issue comments, and CI logs—into the agent's context.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: MEDIUM · 1 issue

  • Runlayer8mo

    1 file scanned · No issues

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at 05ba982. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last month.

Dormantupdated 9 months ago
  • API
  • github
  • gh-cli
  • pull-requests
  • ci
  • workflows
  • issues
  • command-line

README badge

README badge for dimillian/skills/github

Interact with GitHub repositories via the `gh` CLI to check pull request status, view CI runs, fetch workflow logs, and query the GitHub API. Use for tasks like inspecting failed CI steps, listing issues and PRs, or running advanced queries against repository data.

Generated from the current SKILL.md.

Does this skill work outside a git directory?
Yes. Use the `--repo owner/repo` flag with any `gh` command when you're not in a git directory, or pass URLs directly.
Can I query the GitHub API directly with this skill?
Yes. Use `gh api` to access GitHub API endpoints not available through other `gh` subcommands, with `--jq` for filtering JSON output.
What GitHub operations does this skill cover?
Issues, pull requests, CI workflow runs, and direct API queries. You can check PR status, list runs, view run logs, and fetch detailed run information.
Can I debug CI failures with this skill?
Yes. The skill provides a sequence to identify failing checks, find the relevant run ID, view job details, and fetch logs for failed steps only.

Generated from the current SKILL.md. These answers refresh after source changes.