github-issues

Create, triage, label, and manage GitHub issues via gh CLI or REST API.

1|Updated Aug 11, 2026
One-click install
npx skills add https://github.com/Chia1104/agent-air --skill github-issues-chia1104
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-issues
Source: https://github.com/Chia1104/agent-air/tree/main/skills/hermes/github/github-issues
Command: npx skills add https://github.com/Chia1104/agent-air --skill github-issues-chia1104

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Managing GitHub issues manually through the web UI is slow and hard to automate. This Skill provides ready-to-use commands for creating, searching, labeling, assigning, and closing issues directly from the terminal, with both gh CLI and curl REST API fallbacks. ## Core Features & Use Cases - Issue CRUD Operations: Create, view, search, comment on, close, and reopen issues using gh or the GitHub REST API. - Triage Workflow: List untriaged issues, categorize them, apply labels and priorities, and assign owners in a structured process. - Bulk Operations: Batch-close or batch-update issues by combining API calls with shell scripting. - Templates Included: Ready-made bug report and feature request templates for consistent issue formatting. - Use Case: When asked to triage a backlog, list all issues labeled needs-triage, read each one, apply appropriate labels like bug or priority:high, assign owners, and post triage comments — all without leaving the terminal. ## Quick Start Ask the agent to list all open issues labeled bug in the current repository and create a new issue using the bug report template.

Frequently Asked Questions about github-issues

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a GitHub issue from the command line?▼

Use `gh issue create` with --title, --body, --label, and --assignee flags. Without gh, send a POST request with curl to /repos/{owner}/{repo}/issues using your GITHUB_TOKEN for authorization.

How to triage GitHub issues with gh CLI?▼

List untriaged issues with `gh issue list --label "needs-triage" --state open`, read each issue, then apply labels and assignees with `gh issue edit`. Add triage notes using `gh issue comment` when needed.

gh CLI vs GitHub REST API for issue management?▼

The gh CLI offers simpler commands like `gh issue list` and `gh issue close`, while the REST API via curl works anywhere with a GITHUB_TOKEN and no CLI installation. This Skill documents both for every operation.

Can I close multiple GitHub issues at once?▼

Yes, bulk operations combine listing with shell scripting. Pipe issue numbers from `gh issue list --json number --jq` into xargs with `gh issue close`, or loop over curl PATCH requests setting state to closed.

Why does the GitHub issues API return pull requests?▼

The GitHub REST API includes pull requests in the /issues endpoint response. Filter them out by checking for the pull_request key in each item, as shown in the Skill's Python parsing snippets.

What authentication is required for GitHub issue commands?▼

You need either an authenticated gh CLI session or a GITHUB_TOKEN environment variable. The Skill's setup block can also load the token from the Hermes .env file or git credentials.