playbooks

home / skills / kevinslin / llm / dev.gh

dev.gh skill

/skills/dev.gh

This skill helps you manage GitHub tasks efficiently with gh commands, including listing, viewing, and creating issues and pull requests.

npx playbooks add skill kevinslin/llm --skill dev.gh

Review the files below or copy the command above to add this skill to your agents.

Files (1)
skill.md
1.2 KB
---
name: dev.gh
description: GitHub CLI operations
version: 1.0.0
---

You are helping the user with GitHub CLI operations. Use the `gh` command-line tool to perform various GitHub tasks.

## Common Operations

### List outstanding feature issues
```bash
gh issue list --label "feature" --state "open"
```

### List all open issues
```bash
gh issue list --state "open"
```

### List recent pull requests
```bash
gh pr list --state "open"
```

### View issue details
```bash
gh issue view <issue-number>
```

### View PR details
```bash
gh pr view <pr-number>
```

### Create a new issue
```bash
gh issue create --title "Issue title" --body "Issue description"
```

### Check PR status and checks
```bash
gh pr checks
```

### View repository information
```bash
gh repo view
```

## Custom Instructions

- When listing issues or PRs, provide a summary of the results
- For feature issues specifically, use the `--label "feature"` flag
- If no label exists, suggest creating one or searching by keywords in the title/body
- Always show the issue/PR number along with the title for easy reference
- When viewing details, highlight key information like status, assignees, and labels

Overview

This skill helps you run GitHub CLI (gh) commands for common repository workflows. It focuses on listing and inspecting issues and pull requests, creating issues, and checking PR status. The outputs are organized for quick decision making and reference.

How this skill works

The skill issues gh commands to list, view, and create GitHub issues and pull requests. When listing results it summarizes counts and shows each item as "#number — title" for easy reference. When viewing details it extracts and highlights status, assignees, labels, and important metadata.

When to use it

  • Quickly audit open issues or feature requests in a repo
  • Inspect recent or specific pull requests before reviews or merges
  • Create a new issue from the terminal without visiting the web UI
  • Check continuous integration and status checks for a PR
  • Get repository metadata such as default branch and visibility

Best practices

  • Always include the issue/PR number when listing or referencing items
  • Use --label "feature" to isolate feature requests; create the label if it doesn’t exist
  • Summarize results after listing so you can triage at a glance
  • When viewing details, prioritize status, assignees, labels, reviewers, and CI checks
  • If a label is missing, search by keywords in title/body or propose a new standardized label

Example use cases

  • List all open feature requests with: gh issue list --label "feature" --state "open" and review the summary to prioritize work
  • Audit all open issues to find blockers with: gh issue list --state "open" and note #numbers for assignment
  • Create an issue from your terminal: gh issue create --title "Issue title" --body "Issue description" and share #number with the team
  • Check recent PRs before standup: gh pr list --state "open" then view details like assignees and labels for each #number
  • Verify PR checks before merge: gh pr checks to ensure CI passed and list failing checks if any

FAQ

What if the feature label doesn't exist?

Search by keywords in titles or body text, or create a standardized feature label and apply it to relevant issues.

How do I see full details for a specific issue or PR?

Use gh issue view <number> or gh pr view <number> and check highlighted fields: status, assignees, labels, reviewers, and CI status.