list-bugs

Name: list-bugs
Availability: InStock
Author: Semicolon

Fetch open Bug-type issues across GitHub repositories via gh CLI.

Updated Dec 11, 2025

Search Tags:#project management #GraphQL #issue management #GitHub Projects #bug tracking #SEMO #bug list

Ready to run

npx skills add https://github.com/semicolon-devteam/semo --skill list-bugs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: list-bugs
Source: https://github.com/semicolon-devteam/semo/tree/main/semo-skills/list-bugs
Command: npx skills add https://github.com/semicolon-devteam/semo --skill list-bugs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires Bash, gh, jq.

What problem does it solve?

This Skill provides a consistent way to view open bug issues across all repositories by leveraging GitHub Projects' 'Type' field, overcoming the inconsistencies of label-based bug tracking.

Core Features & Use Cases

Unified Bug View: Filters and displays open bug issues based on the GitHub Projects 'Type' field, ensuring a standardized view.
GraphQL Querying: Utilizes GraphQL to efficiently query and aggregate bug data from GitHub Projects.
Formatted Output: Presents bug issues in a clear, tabular format for easy review.
Use Case: To get an immediate overview of all active bugs across your projects, simply ask "버그 이슈 목록 보여줘" and receive a consolidated report.

Quick Start

List all open bugs: "버그 이슈 목록" Check for open bugs: "버그 확인" View Projects bugs: "Projects 버그"

Frequently Asked Questions about list-bugs

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

FAQPage Schema

How do I list all open bugs across multiple GitHub repositories?▼

List open bugs by querying GitHub Projects with the Type field set to Bug and state set to open. This Skill uses the gh CLI and GraphQL to fetch bug issues across all repositories in your organization, displaying them in structured format with issue number, title, type, creation date, and assignees.

Can I use GitHub Projects to track bugs instead of labels?▼

Yes. GitHub Projects' Type field provides consistent bug tracking without relying on label-based approaches. This Skill filters issues by type:Bug to give you a unified bug view across repositories, overcoming the inconsistencies of label-based tracking.

What do I need to set up before listing bugs with the gh CLI?▼

You need the gh CLI installed with authenticated access to your GitHub organization, plus jq for JSON formatting. Ensure your GitHub Projects use the Type field with Bug values so the Skill can query and filter open issues correctly.

How does GraphQL help when querying bugs across repositories?▼

GraphQL efficiently aggregates bug data from GitHub Projects across multiple repositories in a single query. This Skill uses GraphQL to filter by type:Bug and state:open, returning structured rows that you can format and review quickly without multiple API calls.

What output format does this Skill produce for bug issues?▼

The Skill formats bug issues as structured JSON-like rows containing issue number, title, issue type, creation date, and assignee information. This tabular format makes it easy to review all active bugs across your projects at a glance.