github-issues

Manage GitHub issue lifecycles via gh CLI or REST API.

247|22|Updated Dec 11, 2024
One-click install
npx skills add https://github.com/graniet/kheish --skill github-issues-graniet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-issues
Source: https://github.com/graniet/kheish/tree/main/skills/github/github-issues
Command: npx skills add https://github.com/graniet/kheish --skill github-issues-graniet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually tracking, categorizing, and following up on GitHub issues across distributed teams is time-consuming, inconsistent, and often leads to missed bugs or delayed feature requests, especially as issue volume grows.

Core Features & Use Cases

  • Full Issue Lifecycle Management: Create, edit, label, assign, comment on, and close/reopen GitHub issues using either the gh CLI or a curl-based GitHub REST API fallback for environments without gh installed.
  • Triage Automation: Quickly filter untriaged issues, categorize them with relevant labels and priority levels, and assign them to the correct team members to keep backlogs organized.
  • Bulk Administrative Tasks: Run batch operations like closing all issues marked as "won't fix" to reduce repetitive work for project maintainers. Use case: For a software team receiving 50+ weekly bug reports, use this skill to automatically tag new issues with severity labels, assign them to the on-call engineer for the affected service, and close resolved issues in bulk after each sprint.

Quick Start

Use the github-issues skill to list all open issues labeled "bug" and assign the highest-priority one to the on-call backend engineer.

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 for high-volume bug reports?

Automating GitHub issue triage involves filtering untriaged issues, categorizing them with severity labels, and assigning them to the correct team members. This skill handles bulk issue maintenance and triage automation automatically.

Can I manage the full GitHub issue lifecycle via REST API without the gh CLI?

Yes, full GitHub issue lifecycle management is supported via a curl-based GitHub REST API fallback. This allows issue creation, editing, labeling, and state changes in environments without the gh CLI installed, provided authentication is configured.

What is the best way to close multiple GitHub issues in bulk after a sprint?

Closing multiple GitHub issues in bulk is achieved through batch administrative operations. You can run commands to close all issues marked with specific labels like "won't fix" or resolved status, reducing repetitive maintainer work after each sprint.

Does this GitHub issue automation tool support built-in authentication?

Yes, this GitHub issue automation tool supports built-in authentication. It manages credentials natively whether you are using the gh CLI or the curl-based GitHub REST API fallback for issue tracking and management tasks.

How do I log and categorize feature requests on GitHub automatically?

Logging and categorizing feature requests on GitHub automatically requires applying relevant labels and priority levels to new issues. This skill filters and tags incoming feature requests, assigning them to appropriate team members for backlog grooming.