github-triage

Classify GitHub issues and pull requests into categories with evidence-backed reports.

Updated Apr 15, 2026

Search Tags:#github #evidence #issues #triage #report #read-only #pull-requests

Ready to run

npx skills add https://github.com/Juhwa-Lee1023/x-for-github-copilot --skill github-triage-juhwa-lee1023

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: github-triage
Source: https://github.com/Juhwa-Lee1023/x-for-github-copilot/tree/main/source/skills/github-triage
Command: npx skills add https://github.com/Juhwa-Lee1023/x-for-github-copilot --skill github-triage-juhwa-lee1023

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Read-only GitHub issue and PR triage for X for GitHub Copilot CLI. Use when asked to triage open issues or pull requests without taking mutating GitHub actions.

Core Features & Use Cases

Classify open issues and pull requests into categories (bugs, feature requests, questions, PRs ready for review, blocked or risky) and present an evidence-backed report.
Enforce non-mutating policy: no comments, merges, closes, or writes via gh api; all findings cite runtime data (gh output), repository files, and commit history.
Use cases include backlog triage, prioritizing PR reviews, and generating structured briefs for teammates.

Quick Start

Provide the target repository (owner/name or URL); the skill will perform a read-only triage of open issues and PRs and return an evidence-backed report.

Frequently Asked Questions about github-triage

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

FAQPage Schema

How do I triage open GitHub issues and pull requests without making changes to the repository?▼

Read-only GitHub triage classifies open issues and PRs into bugs, feature requests, questions, and review readiness using runtime gh outputs, repository files, and commit history without taking mutating actions like comments or merges.

What is the best way to classify GitHub backlog items into bugs and feature requests?▼

Classify GitHub backlog items by analyzing evidence from repository files and commit history to categorize open issues and PRs into bugs, feature requests, questions, and blocked or risky items for structured triage reports.

Can I use this triage tool for both private and open-source repositories?▼

Yes, GitHub triage applies to both open-source and private repositories to classify open issues and pull requests into categories and present an evidence-backed report without taking mutating GitHub actions.

How do I generate an evidence-backed report for prioritizing PR reviews?▼

Generate an evidence-backed report by providing the target repository owner or URL; the skill performs read-only triage of open PRs using runtime data and commit history to identify items ready for review or blocked.

What are the limitations of using a read-only GitHub triage workflow?▼

Limitations include a strict non-mutating policy that prevents comments, merges, closes, or writes via gh api, meaning all triage findings are observational and require manual action to resolve GitHub issues.