github-triage

Classify GitHub issues and PRs into per-item background tasks.

Updated Feb 19, 2026
One-click install
npx skills add https://github.com/eysenfalk/cerebras --skill github-triage-eysenfalk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-triage
Source: https://github.com/eysenfalk/cerebras/tree/main/.opencode/skills/github-triage
Command: npx skills add https://github.com/eysenfalk/cerebras --skill github-triage-eysenfalk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates and parallelizes triage of GitHub issues and PRs by assigning every item to a separate background task, enabling rapid, scalable review.

Core Features & Use Cases

  • Per-item background tasks: one task per issue or PR for isolation and parallelism.
  • Automated classification and actions: triage questions, bugs, feature requests, etc.
  • Unified workflow for issues and PRs with clear triggers like triage, triage issues, triage PRs, github triage.

Quick Start

Start triaging a repository by triggering the unified GitHub triage workflow to spawn per-item background tasks for issues and PRs.

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 triage for repositories with a large volume of issues and PRs?

Automated GitHub triage fetches open items, classifies them, and spawns a dedicated background task per item to perform actions, enabling scalable and parallel review for large repositories.

What is the best way to parallelize GitHub issue and PR analysis?

The best way to parallelize GitHub issue and PR analysis is assigning every item to a separate background task, ensuring isolation and parallelism for rapid classification and triage actions.

Can I triage GitHub issues and pull requests in a single unified workflow?

Yes, you can triage GitHub issues and PRs using a unified workflow triggered by commands like triage, triage issues, or triage PRs to spawn per-item background tasks.

How does background task isolation work for GitHub triage?

Background task isolation works by mapping each fetched GitHub issue or PR to a dedicated TaskCreate agent, allowing every item to be analyzed and triaged independently in parallel.

Does parallel GitHub triage work for continuous monitoring of open items?

Parallel GitHub triage supports continuous monitoring by repeatedly fetching open items and spawning background tasks to classify and perform actions on new issues and PRs.