github-triage

Classify GitHub issues and PRs and spawn background tasks for triage.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Efficiently triaging GitHub issues and PRs by automatically classifying them and spawning per-item background tasks, reducing manual triage workload and speeding up response times.

Core Features & Use Cases

  • Classify open issues and PRs based on content and labels to determine appropriate actions.
  • Spawn one background task per item (category: free) to analyze, comment, close, merge, or report results.
  • Parallel processing with progress tracking and centralized result collection for auditing and reporting.
  • Use cases include triaging bug reports, feature requests, and questions across large repos with minimal human intervention.

Quick Start

Trigger a triage run on a repository to automatically classify open issues and PRs, then spawn parallel background tasks to analyze each item.

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 for my repository?

To automate GitHub triage, you can trigger a triage run that classifies open issues and pull requests based on content and labels to determine appropriate actions like commenting, closing, or merging.

Can I process open issues and PRs concurrently to speed up triage workflow?

Yes, this approach handles open issues and PRs concurrently by spawning one background task per item, enabling parallel processing with progress tracking to significantly speed up triage across repositories of any size.

How does automated triage classify bug reports and feature requests safely?

Automated triage classifies bug reports and feature requests safely by relying on codebase prompts and read-only analysis to decide whether to comment, close, or merge, ensuring operations remain non-destructive.

What is the best way to manage large-scale GitHub issue classification with minimal human intervention?

The best way to manage large-scale GitHub issue classification is spawning parallel background tasks per item, which provides centralized result collection for auditing and reporting while reducing manual triage workload.

Does automated GitHub triage work with repositories of any size?

Yes, automated GitHub triage applies to repositories of any size, concurrently handling open issues and PRs to minimize human intervention across large repos and accelerate response times.