github-issues

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

Updated May 4, 2026
One-click install
npx skills add https://github.com/Junkfooooood/hermes-governance --skill github-issues-junkfooooood
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-issues
Source: https://github.com/Junkfooooood/hermes-governance/tree/main/skills/github/github-issues
Command: npx skills add https://github.com/Junkfooooood/hermes-governance --skill github-issues-junkfooooood

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 the GitHub REST API. ## Core Features & Use Cases - Full Issue Lifecycle: Create, view, comment on, close, and reopen issues with both gh and curl fallback commands. - Triage Workflow: List untriaged issues, apply labels and priorities, assign owners, and post triage notes in a structured process. - Bulk Operations: Batch-close or batch-update issues by combining API calls with shell scripting. - Use Case: When asked to triage a backlog, list all issues labeled "needs-triage", categorize each one, apply priority labels, assign owners, and comment with triage notes — all without leaving the terminal. ## Quick Start Ask the assistant to create a bug report issue in the current repository titled "Login redirect ignores next parameter" with the bug label.

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. Both approaches support labels and assignees at creation time.

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 comment with triage notes using gh issue comment.

gh CLI vs GitHub REST API for issue management?

The gh CLI offers shorter commands and handles authentication automatically, while the REST API with curl works in environments without gh installed. This Skill provides both variants for every operation, so either tool covers the same functionality.

Does the GitHub issues API also return pull requests?

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

Why is my GitHub API request failing with authentication errors?

Requests fail when GITHUB_TOKEN is unset or gh is not authenticated. Run gh auth status to verify CLI auth, or export GITHUB_TOKEN from ~/.hermes/.env or ~/.git-credentials as described in the setup section.

How do I close multiple GitHub issues at once?

Pipe issue numbers from gh issue list --label "wontfix" --json number into xargs with gh issue close, or loop over curl PATCH requests setting state to closed. The Skill includes complete bulk-operation shell examples for both tools.