github-issues

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

Updated Sep 9, 2026
One-click install
npx skills add https://github.com/luckybbjason1/trading --skill github-issues-luckybbjason1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-issues
Source: https://github.com/luckybbjason1/trading/tree/main/.hermes/skills/github/github-issues
Command: npx skills add https://github.com/luckybbjason1/trading --skill github-issues-luckybbjason1

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 using either the gh CLI or curl with the GitHub REST API. ## Core Features & Use Cases - Issue CRUD Operations: List, view, create, comment on, close, and reopen issues with both gh and curl fallback commands. - Triage Workflow: A structured process for listing untriaged issues, categorizing them, applying labels and priorities, and assigning owners. - Bulk Operations: Shell scripting patterns for batch actions like closing all issues with a specific label. - Templates Included: Ready-made bug report and feature request templates for consistent issue formatting. - Use Case: When asked to triage a backlog, the Skill lists all issues labeled "needs-triage", reads each one, applies appropriate labels and priority, assigns owners, and posts triage comments automatically. ## Quick Start Ask the AI to list all open issues labeled bug in the current repository and create a new bug report issue using the provided 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, or send a POST request to /repos/{owner}/{repo}/issues with a JSON payload containing title, body, labels, and assignees. Both methods require prior GitHub authentication.

How to triage GitHub issues with gh CLI?

List untriaged issues with gh issue list --label "needs-triage" --state open, then read each issue, apply labels with gh issue edit --add-label, assign owners with --add-assignee, and add triage notes with gh issue comment.

gh CLI vs GitHub REST API for issue management?

The gh CLI offers shorter, more readable commands and handles authentication automatically. The REST API with curl works as a fallback when gh is unavailable, requiring a GITHUB_TOKEN and manual JSON parsing with python3.

Does this work without the gh CLI installed?

Yes, every operation includes a curl fallback using the GitHub REST API. The Skill detects authentication automatically, falling back to a GITHUB_TOKEN from the environment, a .env file, or git-credentials.

How do I close multiple GitHub issues at once?

Pipe issue numbers from gh issue list --label "wontfix" --json number --jq into xargs with gh issue close, or loop over curl API results and send PATCH requests setting state to closed for each issue number.