skills.rest
0xtaoist
0xtaoistCOMMUNITY
Explore all skills by this author →
GitHub

ln-911-github-triager

Scan open GitHub issues, PRs, and discussions to produce a prioritized triage report.

Updated Mar 14, 2026
Search Tags:#automation#github#reporting#issues#triage#discussions#pull-requests
One-click install
npx skills add https://github.com/0xtaoist/taogate --skill ln-911-github-triager
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ln-911-github-triager
Source: https://github.com/0xtaoist/taogate/tree/main/ln-911-github-triager
Command: npx skills add https://github.com/0xtaoist/taogate --skill ln-911-github-triager

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scans open GitHub issues, PRs, and discussions in a repository to produce a clear triage report with actionable recommendations and engagement metrics.

Core Features & Use Cases

  • Scans issues, pull requests, and discussions to identify urgency and engagement signals.
  • Classifies items into P0–P4 priorities based on ownership, activity, and labels.
  • Outputs a comprehensive triage report with red flags, health metrics, and recommended actions for maintainers.

Quick Start

Run the triager against a repository to generate a prioritized triage report.

Frequently Asked Questions about ln-911-github-triager

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

FAQPage Schema
How do I generate a prioritized triage report for open GitHub issues and pull requests?▼

To generate a prioritized GitHub triage report, scan open issues, PRs, and discussions in a repository to classify items by priority and engagement metrics. The triager outputs actionable recommendations without modifying any GitHub state.

What is the best way to automate GitHub issue triage and identify stale items?▼

Automated GitHub issue triage identifies stale items by scanning open issues and PRs against a staleness threshold. This process flags neglected items and classifies priority from P0 to P4 based on ownership, activity, and labels.

Can I scan GitHub discussions along with issues and PRs for triage insights?▼

Yes, you can scan GitHub discussions alongside open issues and PRs. The triager accepts scope tokens for issues, PRs, and discussions to comprehensively analyze repository activity and produce tailored engagement metrics.

How does classifying GitHub items into P0–P4 priorities work for maintainers?▼

Classifying GitHub items into P0–P4 priorities works by evaluating ownership, activity levels, and existing labels during the triage scan. Maintainers receive a comprehensive report with red flags, health metrics, and recommended actions.

Does the GitHub triage report modify any repository state when scanning pull requests?▼

No, the GitHub triage report is strictly read-only and never modifies any repository state when scanning pull requests, issues, or discussions. It only analyzes current repository data to output health metrics and recommended actions.

How do I tailor the GitHub triage output for different repository coordinators?▼

Tailor the GitHub triage output by passing scope tokens, a staleness threshold, and a summary flag. This customizes the prioritized report specifically for coordinators and maintainers needing focused engagement metrics and recommended actions.

Related Skills

Explore More Software Engineering Skills→
robertbr123robertbr123

github-auth

Configure GitHub authentication via HTTPS tokens, SSH keys, or gh CLI.

Community
Intermediate
aizhimouaizhimou
1.2k

daily-issue-triage

Generates a daily maintainer report from open GitHub issues using a cursor-based workflow.

Community
Advanced
AndreJorgeLopesAndreJorgeLopes
1

task-prioritize

Move a devflow task markdown file between P0–P4 folders and update its YAML priority.

Community
Basic
gittowergittower
413

sync-repo-status

Generate a repository status snapshot of pull requests, branches, issues, and discussions.

Official
Advanced