github-issues

Manage GitHub issues via gh CLI and REST API operations.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines GitHub issue management so you can create, find, triage, label, assign, comment on, close, and reopen issues without manually navigating the GitHub web interface.

Core Features & Use Cases

  • Issue Discovery: List, filter, search, and inspect issues by state, label, assignee, or keywords.
  • Issue Creation: Open well-structured bug reports and feature requests using GitHub CLI or the REST API.
  • Triage and Maintenance: Apply labels, assign owners, add comments, and manage issue lifecycle actions like closing, reopening, and bulk updates.
  • Use Case: A product or engineering team can quickly triage a backlog of unlabelled issues, assign ownership, and close resolved items in bulk.

Quick Start

Ask me to triage open GitHub issues in the current repository and label, assign, or close them based on their content.

Frequently Asked Questions about github-issues

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

FAQPage Schema
How do I triage and manage GitHub issues in bulk without using the web interface?

You can triage GitHub issues in bulk by applying labels, assigning owners, and closing resolved items using either the gh CLI or the GitHub REST API for repository-scoped management.

What's the best way to search and filter open GitHub bug reports by assignee or label?

Filtering open GitHub bug reports is done by listing, searching, and inspecting issues by state, label, assignee, or keywords through the GitHub REST API or gh CLI operations.

Do I need GitHub authentication to create and manage repository tickets via the CLI?

Yes, GitHub authentication is required to create, label, assign, comment on, close, and reopen repository tickets using both gh CLI and REST API operations.

Can I use this to clear a backlog of unlabelled GitHub feature requests and assign ownership?

Yes, you can clear a backlog of unlabelled GitHub feature requests by applying labels, assigning ownership, and performing bulk maintenance actions on repository tickets.

Does this approach support both gh CLI and GitHub REST API operations for issue lifecycle management?

Yes, issue lifecycle management supports both gh CLI and GitHub REST API operations to create, comment on, close, and reopen repository tickets for software teams.

Why use automated issue triage workflows for software engineering teams?

Automated issue triage workflows streamline bug tracking and backlog cleanup for software teams, allowing you to find, label, assign, and close GitHub issues without manual web navigation.