# Gh CLI

> Use when the user needs to interact with GitHub — checking CI status, viewing PRs, listing issues, querying the API, or any GitHub-related task. Triggers include "check CI", "list PRs", "view issue", "GitHub API", or any request involving repositories, pull requests, issues, or workflows.

- Skill: `clawrun-sh/gh-cli` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add clawrun-sh/gh-cli`
- Raw SKILL.md: https://api.skillmd.com/api/skills/clawrun-sh/gh-cli/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: clawrun-sh (https://skillmd.com/u/clawrun-sh)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/clawrun-sh/gh-cli

---


# 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)"'
```