github-triage

Classify GitHub issues and pull requests into background triage tasks.

4|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/EZotoff/ez-omo-config --skill github-triage-ezotoff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-triage
Source: https://github.com/EZotoff/ez-omo-config/tree/main/skills/github-triage
Command: npx skills add https://github.com/EZotoff/ez-omo-config --skill github-triage-ezotoff

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the repetitive and time-consuming work of reviewing, classifying, and acting on open GitHub issues and pull requests so maintainers can scale repository maintenance without manual per-item triage.

Core Features & Use Cases

  • Exhaustive Fetching: Retrieves all open issues and PRs via gh CLI or bundled fetch scripts with pagination to ensure no items are missed.
  • Deterministic Classification: Classifies each item into question, bug, feature, or PR types using title, labels, and body heuristics.
  • One-task-per-item Orchestration: Spawns exactly one background subagent per item with category="quick", tracks progress via todowrite, and collects results through background_output polling.
  • Actionable Outcomes: Subagents can comment, request changes, recommend actions, and auto-merge strictly safe bugfix PRs under defined merge conditions.
  • Safety & Guardrails: Enforces strict anti-patterns (never checkout PR branches, mandatory comment prefixes, never guess root causes) to reduce risky automation.

Quick Start

Invoke the github-triage skill to triage all open issues and pull requests in the repository and produce a summarized report.

Frequently Asked Questions about github-triage

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

FAQPage Schema
How do I automate triaging open GitHub issues and pull requests at scale?

Automating GitHub triage involves classifying open issues and PRs into categories like bugs, questions, or features, then spawning a background handler per item to comment, request changes, or merge safe bugfixes.

How does automated GitHub triage classify issues and pull requests?

Automated triage classifies GitHub issues and PRs by analyzing the item title, labels, and body heuristics to categorize them as questions, bugs, features, or PR types for targeted background processing.

Can I automatically merge low-risk bugfix pull requests without manual review?

Yes, you can automatically merge low-risk bugfix pull requests by configuring background subagents to enforce strict safety conditions and merge rules, ensuring only safe PRs are merged without manual intervention.

Does automated GitHub triage require the gh CLI to fetch open issues?

Automated GitHub triage relies on the gh CLI or bundled fetch scripts with pagination to retrieve all open issues and PRs, ensuring no repository items are missed during the exhaustive fetching process.

What safety guardrails prevent risky automated actions during pull request triage?

Safety guardrails for pull request triage enforce strict anti-patterns like never checking out PR branches, mandating comment prefixes, and never guessing root causes to reduce risky automated actions.

How do I track the progress of background tasks spawned for GitHub triage?

Track GitHub triage background task progress by using todowrite to monitor spawned subagents and collecting their results through background_output polling to aggregate the final triage report.