github-issues

Manage GitHub issues via CLI or REST for triage workflows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you manage GitHub issues without manually clicking through the UI, reducing time spent on reporting, labeling, assigning, commenting, and triaging bugs or requests.

Core Features & Use Cases

  • View and search issues: List, filter by label/assignee/state, and read full issue details (including bodies) for faster investigation.
  • Create and standardize issue reports: Create issues with titles, detailed Markdown bodies, labels, and assignees using either the GitHub CLI or REST.
  • Triage and maintain momentum: Add/remove labels, assign owners, comment with updates, and close/reopen issues (plus bulk operations by label).
  • Use Case: When a user reports an authentication bug, use this Skill to search matching issues, create a well-structured bug report, label it (e.g., bug/authentication), and assign it to the right maintainer.

Quick Start

Tell the Skill to create a new GitHub issue in the current repository using your GitHub credentials, with a clear title, a Markdown bug template, and the right labels and assignee.

Frequently Asked Questions about github-issues

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

FAQPage Schema
How do I automate GitHub issue triage and labeling without using the web UI?

You can automate GitHub issue triage by using CLI commands or REST API calls to search, label, assign, comment on, and close issues programmatically. This Skill handles repository-based maintenance workflows like bug reporting and backlog cleanup without manual UI interaction.

What's the best way to create standardized GitHub bug reports with Markdown templates?

Creating standardized GitHub bug reports is done by providing a title, detailed Markdown body, labels, and assignees through either the GitHub CLI or REST API. This Skill structures issue creation to ensure consistent bug reporting and feature request formats across your repository.

Can I bulk close or relabel GitHub issues filtered by assignee or state?

Bulk GitHub issue operations are supported by filtering issues based on label, assignee, or state, then applying actions like closing, reopening, or modifying labels across the matched set. This enables efficient backlog maintenance and bulk triage directly via CLI or token-authorized API calls.

Do I need a GitHub token or CLI authentication to manage issues via REST API?

An authenticated GitHub context is required to manage issues, using either the GitHub CLI commands or token-authorized REST API calls. Correct discovery of the repository owner and name is also necessary for the API calls to target the appropriate repository workflows.

How does issue assignment and commenting work for maintaining backlog momentum?

Issue assignment and commenting maintain backlog momentum by allowing you to assign specific owners, add update comments, and modify labels on existing issues. This Skill facilitates these actions via CLI or REST to keep triage workflows moving and ensure issues reach the right maintainers.

Why are my GitHub API calls failing when searching for repository issues?

GitHub API calls for searching issues fail when the authenticated context lacks proper repository owner and name discovery or valid token authorization. Ensure your GitHub credentials are correctly configured and the repository target is accurately identified before executing triage or creation commands.