github-issues

Manage GitHub issues via gh or curl across repositories.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/cloudliness/Hermes-Autonomous-AI-Agent-Dialed-In-For-Windows-11 --skill github-issues-cloudliness
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-issues
Source: https://github.com/cloudliness/Hermes-Autonomous-AI-Agent-Dialed-In-For-Windows-11/tree/main/skills/github/github-issues
Command: npx skills add https://github.com/cloudliness/Hermes-Autonomous-AI-Agent-Dialed-In-For-Windows-11 --skill github-issues-cloudliness

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GitHub issue management can be tedious and error-prone when done entirely in the UI. This skill automates common workflows by providing a consistent, CLI-based approach via gh and curl to create, search, triage, label, assign, comment on, and close issues.

Core Features & Use Cases

  • Create, search, triage, and manage issues across one or more repositories using gh or curl.
  • Label, assign, view, comment, and close issues, with a clear path when one tool is unavailable.
  • Use case: A developer triages a backlog by listing open issues, filtering by labels, applying ownership, and documenting decisions via comments.

Quick Start

Ask it to list open issues in the current repository using gh or curl.

Frequently Asked Questions about github-issues

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

FAQPage Schema
Can I triage and bulk update GitHub issues across multiple repositories?

GitHub issue triage can be automated with gh or curl by listing open issues, filtering by labels, applying ownership, and documenting decisions via comments. This streamlines backlog management across single or multiple repositories.

What is the best way to cross-reference GitHub issues with pull requests using CLI?

You do not strictly need a local git repository to manage issues via curl or gh, but you must provide explicit owner and repo arguments if you are not operating inside a local git directory with a GitHub remote.

Why use gh instead of curl for automating GitHub issue workflows?

Cross-referencing GitHub issues with pull requests is handled through explicit API calls via curl or gh commands. This enables automated linking and tracking between related issues and their corresponding PRs.

What are the prerequisites for authenticating to the GitHub API for issue automation?

Using gh instead of curl for GitHub issue workflows provides a clear path when you need to handle authentication and complex API interactions natively. The skill supports both tools, offering a fallback mechanism if one is unavailable.

What are the prerequisites for authenticating to the GitHub API for issue automation?

The prerequisite for GitHub API issue automation is valid authentication configured for your gh or curl environment. This ensures secure access to view, create, and modify issues across your specified repositories.