github-triage

Fetch and classify open GitHub issues and pull requests into reports.

67.6k|5.5k|Updated Dec 3, 2025
One-click install
npx skills add https://github.com/code-yeongyu/oh-my-openagent --skill github-triage-code-yeongyu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-triage
Source: https://github.com/code-yeongyu/oh-my-openagent/tree/main/.opencode/skills/github-triage
Command: npx skills add https://github.com/code-yeongyu/oh-my-openagent --skill github-triage-code-yeongyu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires typer, rich, and includes scripts (resource) components.

What problem does it solve?

This Skill automates the initial triage of GitHub issues and pull requests, classifying them and preparing initial analysis reports without taking any action on GitHub.

Core Features & Use Cases

  • Automated Classification: Identifies issues and PRs as bugs, feature requests, questions, or other types.
  • Read-Only Analysis: Fetches and analyzes open items, generating detailed reports with evidence-backed claims.
  • Zero-Action Policy: Strictly adheres to not making any changes on GitHub (no comments, merges, closes, etc.).
  • Use Case: When a new bug report is filed, this Skill can automatically analyze the issue, search the codebase for potential causes or existing fixes, and generate a report for a maintainer to review.

Quick Start

Use the github-triage skill to analyze all open issues and pull requests in the current repository.

Frequently Asked Questions about github-triage

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

FAQPage Schema
How do I automate GitHub issue and pull request triage without making changes to the repository?

Automating GitHub issue and PR triage fetches all open items and classifies them as bugs, feature requests, or questions without mutating the repository. It generates evidence-backed reports with GitHub permalinks to a temporary directory for maintainer review.

Can I automatically analyze open GitHub issues to identify bugs and search the codebase for causes?

Automated issue analysis fetches open GitHub issues and classifies them by type. It analyzes each item and generates detailed reports containing evidence-backed claims with GitHub permalinks, allowing maintainers to review potential codebase causes or existing fixes.

Does automated GitHub triage require write permissions to comment on or close issues and pull requests?

Automated GitHub triage requires only read-only access and operates under a strict zero-action policy. It does not make any GitHub mutations, meaning it will not post comments, merge pull requests, or close issues during the analysis process.

What is the best way to generate evidence-backed reports for open GitHub pull requests?

Generating evidence-backed reports for open GitHub pull requests involves fetching and analyzing each item individually. The process spawns a quick background subagent per pull request to classify the item and write a detailed report to the temporary directory.

How do I classify open GitHub issues into categories like feature requests and bug reports?

Classifying open GitHub issues involves a read-only triage process that fetches all open items and categorizes them as bugs, feature requests, questions, or other types. It then prepares initial analysis reports for each classified item.

Are there limitations to automated GitHub triage regarding repository mutations?

Automated GitHub triage is strictly limited to read-only operations and cannot perform any repository mutations. It will not comment, merge, close, or modify any issues or pull requests, functioning entirely as a background analysis task that only generates local reports.