github-issues

List, create, label, assign, comment on, and close GitHub issues via gh or REST.

11|Updated May 17, 2026
One-click install
npx skills add https://github.com/StarryCod/cogitum --skill github-issues-starrycod
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-issues
Source: https://github.com/StarryCod/cogitum/tree/main/cogitum/data/skills/github/github-issues
Command: npx skills add https://github.com/StarryCod/cogitum --skill github-issues-starrycod

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps software teams streamline GitHub issue management by providing a unified approach to viewing, triaging, labeling, and assigning issues using gh or the REST API, reducing manual context switching.

Core Features & Use Cases

  • View issues across repositories with filters for state, labels, and assignees to triage quickly.
  • Create issues, add labels, assign owners, and post comments to keep work moving.
  • Use cases include triaging bugs in busy projects, coordinating feature requests, and tracking progress across multiple repositories.

Quick Start

List open issues for the current repository using gh or REST to begin triaging.

Frequently Asked Questions about github-issues

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

FAQPage Schema
How do I triage GitHub issues across multiple repositories?

To triage GitHub issues, you can list open items across repositories using filters for state, labels, and assignees, enabling rapid categorization and status updates without manual context switching.

Can I create and assign GitHub issues using gh or REST API?

Yes, you can create issues, add labels, assign owners, and post comments using either gh or the REST API to keep work moving across standard OSS project workflows.

What is the best way to automate labeling and assignment for GitHub issues?

Automate GitHub issue labeling and assignment by applying filters and operations through gh or REST, streamlining the management of bugs and feature requests in busy projects.

Do I need gh installed to manage GitHub issues?

You do not need gh exclusively, as issue management operations like listing, viewing, and closing are fully supported via the GitHub REST API as an alternative.

How does viewing and closing GitHub issues work with gh or REST?

Viewing and closing GitHub issues involves calling specific operations via gh or REST to surface issue details and update the state from open to closed as needed.

When should I use REST instead of gh for GitHub issue triage?

Use the REST API instead of gh for GitHub issue triage when integrating issue operations like labeling or commenting directly into custom automation scripts or environments lacking the CLI.