github-triage

Classify GitHub issues and pull requests and spawn background subagents for triage actions.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/D4ch1au/evil-oh-my-openagent --skill github-triage-d4ch1au
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-triage
Source: https://github.com/D4ch1au/evil-oh-my-openagent/tree/main/.opencode/skills/github-triage
Command: npx skills add https://github.com/D4ch1au/evil-oh-my-openagent --skill github-triage-d4ch1au

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of managing GitHub issues and pull requests by automatically classifying, triaging, and taking initial actions on them, freeing up maintainers' time.

Core Features & Use Cases

  • Unified Triage: Handles both issues and PRs with a single workflow.
  • Automated Classification: Identifies issue types (question, bug, feature) and PR types (bugfix, other).
  • Background Processing: Spawns individual background tasks for each item, allowing parallel processing.
  • Actionable Insights: Subagents can answer questions, confirm bugs, assess features, or merge safe bugfix PRs.
  • Use Case: Automatically review all new bug reports, confirm if they are indeed bugs by checking the codebase, and merge simple bugfix PRs, while flagging complex issues for human review.

Quick Start

Use the github-triage skill to process 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?

You can automate GitHub triage by running a skill that classifies issues and PRs into types like bug, question, or bugfix, then spawns background subagents to analyze and take initial actions. It uses the gh CLI to fetch repository items and process them in parallel.

Can I automatically merge safe bugfix pull requests?

Yes, the automated triage process identifies PRs as bugfixes and spawns dedicated subagents to assess them. Safe bugfix PRs can be automatically merged, while complex changes are flagged for human review.

Does this GitHub triage process require the gh CLI?

Yes, the gh CLI is required. The triage workflow leverages the gh CLI to fetch and interact with repository items, categorizing them to automate responses, bug confirmation, and PR merging.

How does automated bug confirmation work for GitHub issues?

Automated bug confirmation works by classifying issues as bugs and spawning background subagents. These subagents analyze the issue by checking the codebase to confirm if the bug is valid before taking further action.

What is the best way to handle high volumes of open GitHub issues and PRs?

The best way to handle high volumes is using a unified triage workflow that processes items in parallel. It automatically categorizes issues and PRs, answers questions, confirms bugs, and assesses features to free up maintainer time.

Can I classify GitHub issues into different categories automatically?

Yes, automated classification categorizes GitHub items into types including ISSUE_QUESTION, ISSUE_BUG, and PR_BUGFIX. This allows the system to trigger appropriate automated responses and actions based on the specific item type.