github-issues

List and group open GitHub Issues by label with gh CLI.

1|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/dobachi/claude-skills-marketplace --skill github-issues-dobachi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-issues
Source: https://github.com/dobachi/claude-skills-marketplace/tree/main/plugins/github-issues/skills/github-issues
Command: npx skills add https://github.com/dobachi/claude-skills-marketplace --skill github-issues-dobachi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes the effort of manually scanning GitHub Issues by quickly listing, categorizing, and prioritizing open work so you can focus on what matters next.

Core Features & Use Cases

  • Open Issue Listing: Retrieves recent open Issues with numbers, titles, labels, assignees, and creation dates.
  • Label Aggregation: Groups Issues by label and surfaces the most common categories to clarify themes.
  • Priority & Recency Triage: Highlights high-priority Issues (based on labels) and identifies recently created items to accelerate planning.

Quick Start

Run /github-issues to list open Issues, group them by label, highlight high-priority items, and suggest an implementation-friendly organization.

Frequently Asked Questions about github-issues

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

FAQPage Schema
How do I organize GitHub issues by label for backlog grooming?

Triage GitHub issues by listing open items, aggregating them by label, and surfacing high-priority and recently created work. It uses gh issue list with JSON fields and jq-based grouping to clarify themes, accelerating repository task triage and planning sessions.

Do I need GitHub CLI authentication to list and prioritize issues?

Yes, GitHub CLI authentication is required to retrieve and prioritize issues. The Skill uses gh issue list with JSON fields, jq-based grouping, and time-based search constraints to securely fetch open items for repository task triage.

What is the best way to surface high-priority GitHub issues during planning?

Surface high-priority GitHub issues by filtering based on labels and identifying recently created items. The tool highlights high-priority work and recent activity to suggest an implementation-friendly organization for planning sessions.

Can I group GitHub issues by assignee and creation date for task triage?

Group GitHub issues by retrieving recent open items with numbers, titles, labels, assignees, and creation dates. It primarily aggregates by label using jq but includes assignee and creation date data to accelerate task triage.

What are the limitations of using jq-based grouping for GitHub issue aggregation?

jq-based grouping for GitHub issue aggregation is limited to the JSON fields returned by gh issue list. It focuses on open items, label aggregation, and time-based search constraints, so closed issues or fields beyond the standard JSON output are not surfaced.