github-issues

Automate GitHub issue creation, triage, and management via CLI or REST API.

1|Updated Feb 17, 2026
One-click install
npx skills add https://github.com/brittaniebuffiecsu/zerogravityclaw --skill github-issues-brittaniebuffiecsu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-issues
Source: https://github.com/brittaniebuffiecsu/zerogravityclaw/tree/main/src/hermes-core/skills/github/github-issues
Command: npx skills add https://github.com/brittaniebuffiecsu/zerogravityclaw --skill github-issues-brittaniebuffiecsu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, curl, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of managing GitHub issues, reducing the time and effort required to create, triage, and track issues.

Core Features & Use Cases

  • Issue Creation: Create and manage issues directly through the command line.
  • Issue Triage: Triage and categorize issues for efficient management.
  • Issue Management: Assign labels, add comments, and close/reopen issues as needed.

Quick Start

Use the github-issues skill to list all open issues in your current GitHub repository.

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 creation and triage from the command line?

You can automate GitHub issue creation and triage using the 'gh' command-line interface to directly manage issues, assign labels, and add comments without switching to the web interface.

Can I manage GitHub issues using the REST API instead of the CLI?

Yes, you can manage GitHub issues via the REST API using 'curl' to interact with GitHub repositories, providing an alternative to the 'gh' command-line method for issue tracking.

Do I need the GitHub CLI installed to track bugs with this issue management workflow?

You need either the 'gh' GitHub CLI for command-line operations or 'curl' for REST API interactions to execute bug tracking and issue management tasks within your repository.

What is the best way to categorize and assign labels to open GitHub issues in bulk?

The best way to categorize and assign labels to open GitHub issues is by using automated command-line scripts to triage issues, ensuring efficient management and tracking for development teams.

Are there limitations when using curl for GitHub issue tracking instead of gh?

Using 'curl' for GitHub issue tracking requires manual construction of API requests and authentication headers, whereas 'gh' natively handles repository context, making 'curl' more verbose for complex issue triage.