github-triage

Generate read-only markdown triage reports for GitHub issues and pull requests.

10|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/Lee-SiHyeon/oh-my-copilot --skill github-triage-lee-sihyeon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-triage
Source: https://github.com/Lee-SiHyeon/oh-my-copilot/tree/main/.github/skills/github-triage
Command: npx skills add https://github.com/Lee-SiHyeon/oh-my-copilot --skill github-triage-lee-sihyeon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you quickly assess GitHub issues and pull requests by generating structured triage reports without making any changes to the repository, saving maintainers time on initial review.

Core Features & Use Cases

  • Zero-action safety: Enforces a strict policy that forbids commenting, editing, closing, merging, reviewing, or sending non-GET API requests, while allowing read-only inspection and local report writing.
  • Bulk, parallel analysis: Fetches open issues and PRs (up to configured limits), then processes each item in parallel to produce one report per item.
  • Evidence-first reporting: Produces category-specific markdown reports (Bug/Question/PR formats) and emphasizes permalinked code references to reduce speculation.
  • Use case: When your repo receives many new open issues/PRs, run the Skill to generate a complete triage snapshot under /tmp so you can prioritize what needs maintainer attention.

Quick Start

Ask an AI to run the github-triage skill to analyze all open issues and PRs for the current GitHub repository and write read-only triage reports to /tmp.

Frequently Asked Questions about github-triage

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

FAQPage Schema
How do I generate read-only triage reports for GitHub issues and pull requests?

To generate read-only triage reports for GitHub issues and pull requests, run the github-triage skill to fetch open items in parallel and write one markdown report per item to a local /tmp directory. It performs bug identification, question classification, and PR risk analysis without making any repository changes.

Does this GitHub issue triage process modify repository state or leave comments?

No, this GitHub issue triage process enforces strict zero-action constraints that forbid commenting, editing, closing, merging, or sending non-GET API requests. It only performs read-only GitHub API fetches and writes local markdown files to /tmp.

What is the best way to prioritize maintainer attention for many open GitHub pull requests?

The best way to prioritize maintainer attention for many open GitHub pull requests is to generate a complete triage snapshot using read-only analysis. The skill processes items in parallel and produces category-specific markdown reports with commit-based permalink evidence to reduce speculation.

How are code references linked in the markdown triage reports for issue analysis?

Markdown triage reports for issue analysis use commit-based permalink evidence to link code references. This evidence-first reporting approach ensures that bug identification and PR merge recommendations are grounded in permanent, verifiable GitHub links rather than speculation.

Can I analyze all open issues and PRs in my repository in bulk?

Yes, you can analyze open issues and PRs in bulk up to configured limits. The skill fetches items in parallel and processes each one individually to produce one dedicated markdown triage report per item, creating a complete repository maintenance snapshot in /tmp.