github · git:20261020.3598af2 · 2026-10-20 · sha256 6f867591584a2e4d

github git:20261020.3598af2A

Immutable. This exact content never changes and is served at /api/v1/blob/6f867591584a2e4d.

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_u3oyaopeayk2oduu/6f867591584a2e4d29ad144afb49036ae7f30ef11a20790afbb626ff27f380a0.json

Then /plugin install github@markdownregistry-u3oyaopeayk2oduu in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.

---
name: github
description: "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."
metadata: {"requires":{"bins":["gh"]}}
---

# 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:
```bash
gh pr checks 55 --repo owner/repo
```

List recent workflow runs:
```bash
gh run list --repo owner/repo --limit 10
```

View a run and see which steps failed:
```bash
gh run view <run-id> --repo owner/repo
```

View logs for failed steps only:
```bash
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:
```bash
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:

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