github-issues

Create, search, and manage GitHub issues with labels, assignments, and comments.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/JKhyro/HERMES-AGENT --skill github-issues-jkhyro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-issues
Source: https://github.com/JKhyro/HERMES-AGENT/tree/main/skills/github/github-issues
Command: npx skills add https://github.com/JKhyro/HERMES-AGENT --skill github-issues-jkhyro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the friction of manual issue tracking by helping you search, create, organize, and resolve GitHub issues from a single workflow.

Core Features & Use Cases

  • Issue Lifecycle Management: Create, view, update, reopen, and close issues with consistent, repeatable steps.
  • Triage and Routing: Add labels, assign owners, filter by status, and comment with triage notes to keep repositories organized.
  • Repository Workflow Support: Link issues to pull requests, use templates for bug reports and feature requests, and handle batch maintenance tasks across a project.
  • Use Case: A maintainer can quickly list untriaged issues, apply priorities, assign the right teammate, and close completed work without leaving the issue workflow.

Quick Start

Ask the assistant to search, create, label, assign, comment on, or close GitHub issues in your repository, using gh first and curl when gh is unavailable.

Frequently Asked Questions about github-issues

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

FAQPage Schema
How do I manage GitHub issues like triage and labeling from a single workflow?

You can manage GitHub issues by searching, creating, triaging, labeling, and assigning them through a unified workflow. This handles the complete issue lifecycle, from filtering unassigned tickets to adding priority labels and routing them to the correct owners.

Can I create and close GitHub issues using gh CLI commands?

Yes, you can create and close GitHub issues using gh CLI commands. The workflow relies on authenticated GitHub access via the gh CLI first, automatically falling back to curl-based GitHub REST API requests when the gh CLI is unavailable.

What is the best way to link GitHub issues to pull requests for repository maintenance?

Linking GitHub issues to pull requests is handled through dedicated repository maintenance workflows. This process connects issue tracking directly to code changes, allowing maintainers to associate bug reports or feature requests with their resolving pull requests.

Do I need authenticated GitHub access to search and update GitHub issues?

Yes, authenticated GitHub access is required to search, create, update, and manage GitHub issues. This authentication ensures secure operations when interacting with repository data using either the gh CLI or curl-based REST API fallbacks.

Does this issue tracking workflow support batch maintenance tasks across a repository?

Yes, the GitHub issue workflow supports batch maintenance tasks across a repository. You can handle bulk operations like applying standard labels, assigning multiple owners, and commenting on grouped tickets to keep the project organized.

Why use curl-based REST API fallbacks when gh CLI is unavailable for GitHub issues?

Using curl-based REST API fallbacks for GitHub issues ensures reliable operations when the gh CLI is missing or fails. This dual approach guarantees that issue search, creation, and triage processes continue without interruption across different environments.