github-issue-triage

Name: github-issue-triage
Availability: InStock
Author: hackefeller

Fetch GitHub issues with pagination and generate categorized triage reports.

1|Updated Feb 23, 2026

Search Tags:#automation #github #reporting #issues #triage #bug tracking

Ready to run

npx skills add https://github.com/hackefeller/ghostwire --skill github-issue-triage-hackefeller

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: github-issue-triage
Source: https://github.com/hackefeller/ghostwire/tree/main/.opencode/skills/github-issue-triage
Command: npx skills add https://github.com/hackefeller/ghostwire --skill github-issue-triage-hackefeller

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of triaging GitHub issues, ensuring that no critical bugs or feature requests are missed and that community engagement is managed effectively.

Core Features & Use Cases

Exhaustive Issue Fetching: Retrieves all issues within a specified time range using robust pagination.
Parallel Analysis: Launches individual background agents for each issue to analyze them concurrently.
Categorized Reporting: Generates a comprehensive report categorizing issues by urgency and action required.
Use Case: Automatically triage all new issues reported in a busy open-source project over the last 48 hours, categorizing them into critical bugs, feature requests, and those that can be closed immediately.

Quick Start

Use the github-issue-triage skill to analyze all issues in the current repository from the last 72 hours.

Frequently Asked Questions about github-issue-triage

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

FAQPage Schema

How do I automate GitHub issue triage for a busy repository?▼

Automating GitHub issue triage involves fetching issues within a time range using exhaustive pagination and launching parallel background agents for analysis. This Skill categorizes issues by type, status, and community engagement, producing a structured report with recommended actions and draft responses.

What is the best way to categorize GitHub issues by urgency and action required?▼

The best way to categorize GitHub issues by urgency is by launching parallel background agents to analyze each issue concurrently. This method identifies critical bugs, feature requests, and community engagement levels, generating a categorized report with recommended actions and draft responses.

Can I generate draft responses for community engagement on GitHub issues?▼

You can generate draft responses for community engagement by analyzing issues concurrently with parallel background agents. The Skill identifies linked PRs and community engagement levels to produce a structured report that includes recommended actions and draft responses.

Does this issue triage process handle large volumes of issues over a specific time range?▼

This issue triage process handles large volumes by using exhaustive pagination to retrieve all issues within a defined time range. It then launches individual parallel background agents for each issue to analyze them concurrently without missing critical bugs.

How does parallel analysis work when triaging GitHub bug tracking reports?▼

Parallel analysis during GitHub bug tracking triage works by launching individual background agents for each fetched issue. This concurrent processing categorizes issues by type and status, identifies linked PRs, and produces a structured report with recommended actions and draft responses.

When do I need to use an automated issue triage report for bug tracking?▼

You need automated issue triage reporting when managing a busy open-source project to ensure no critical bugs or feature requests are missed. It categorizes issues over a defined time range, such as the last 48 hours, and manages community engagement effectively.