github-triage

Triage GitHub issues and pull requests through labeling, validation, and security-gated merging.

4|1|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/prime-radiant-inc/github-triage --skill github-triage-prime-radiant-inc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-triage
Source: https://github.com/prime-radiant-inc/github-triage/tree/main/skills/github-triage
Command: npx skills add https://github.com/prime-radiant-inc/github-triage --skill github-triage-prime-radiant-inc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of managing GitHub issues and pull requests, ensuring that all items are properly categorized, validated, and reviewed, thereby improving project maintainability and developer efficiency.

Core Features & Use Cases

  • Automated Labeling: Discovers patterns, proposes taxonomies, creates labels, and tags issues/PRs.
  • Issue Validation: Checks if open issues are still relevant against the codebase and closes resolved ones.
  • PR Review Workflow: Includes a security-gated review process, local testing, and merging.
  • Use Case: A project maintainer can use this Skill to automatically organize a backlog of 500+ open issues and PRs, ensuring no critical bug is missed and all new contributions are securely and correctly merged.

Quick Start

Use the github-triage skill to perform a full triage workflow on the OWNER/REPO 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 triage and pull request labeling for a large backlog?

Automating GitHub issue triage involves discovering patterns, proposing taxonomies, creating labels, and tagging issues and PRs systematically. This process uses parallel agent execution and GitHub CLI commands to efficiently categorize and validate large backlogs against the codebase.

What is the best way to validate open GitHub issues against the codebase and close resolved ones?

Validating open GitHub issues against the codebase requires checking if the reported problems are still relevant to the current code. Automated triage workflows can systematically review open issues, verify their validity against repository changes, and automatically close resolved or outdated items.

Can I use GitHub CLI commands to set up a security-gated pull request review and merge workflow?

Yes, you can establish a security-gated pull request review and merge workflow using GitHub CLI commands. This workflow integrates local testing and security checks before merging, ensuring new contributions are securely validated and correctly integrated into the main codebase.

How does automated GitHub labeling handle taxonomy proposal and pattern discovery for issues?

Automated GitHub labeling handles taxonomy proposal by discovering existing patterns within issues and pull requests. It analyzes repository content to propose a structured taxonomy, creates corresponding labels, and systematically tags items to improve project maintainability and organization.

Do I need parallel agent execution to manage 500+ open issues and pull requests on GitHub?

Parallel agent execution is highly beneficial for managing 500+ open GitHub issues and pull requests. It enables the triage system to process discovery, validation, and tagging phases concurrently, significantly improving efficiency and safety when handling large-scale project maintenance.