github

GitHub Skill

Full GitHub operations via the gh CLI. Always check auth first, use templates for consistency, and respect rate limits.

Step 0: Auth Detection (ALWAYS FIRST)

Before ANY GitHub operation, detect the auth method:

gh auth status 2>&1

If authenticated: Proceed. Note the logged-in username for the session.

If not authenticated: Check for GITHUB_TOKEN env var:

echo "${GITHUB_TOKEN:+token_set}"

If no token either: Tell the user:

GitHub CLI is not authenticated. Run gh auth login to authenticate, or set GITHUB_TOKEN environment variable with a personal access token.

Do NOT proceed without auth. Do NOT fall back to curl or http_request.

Step 1: Rate Limit Check (before bulk operations)

Before operations that issue 5+ API calls (batch triage, bulk label, multi-issue create), check rate limits:

gh api rate_limit --jq '.resources.core.remaining, .resources.core.limit, .resources.search.remaining, .resources.search.limit'

If core remaining < 100 or search remaining < 10, warn the user and ask whether to proceed.

Issue Operations

Create Issue

gh issue create --repo OWNER/REPO --title "TITLE" --body "BODY" --label "LABEL" --assignee "USER"

Templates (use unless user provides their own):

Bug report:

## Description

[What happened]

## Steps to Reproduce

1. [Step 1]
2. [Step 2]

## Expected Behavior

[What should happen]

## Actual Behavior

[What actually happened]

## Environment

- OS: [e.g., macOS 14.3]
- Version: [e.g., v0.3.70]

Feature request:

## Problem

[What problem does this solve?]

## Proposed Solution

[How should it work?]

## Alternatives Considered

[What else was considered?]

## Additional Context

[Screenshots, logs, references]

List Issues

gh issue list --repo OWNER/REPO --state open --limit 20
gh issue list --repo OWNER/REPO --label "bug" --state open
gh issue list --repo OWNER/REPO --assignee "@me"