github-triage

Generate read-only triage reports for GitHub issues and PRs.

Updated Jun 11, 2026
One-click install
npx skills add https://github.com/HaydernCenterpoint/Codex-Skills --skill github-triage-hayderncenterpoint
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-triage
Source: https://github.com/HaydernCenterpoint/Codex-Skills/tree/main/skills/github-triage
Command: npx skills add https://github.com/HaydernCenterpoint/Codex-Skills --skill github-triage-hayderncenterpoint

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Read-only GitHub triage analyzes open issues and PRs, generating evidence-backed reports without mutating GitHub state.

Core Features & Use Cases

  • 1 item = 1 background task, enabling scalable triage of each open item.
  • Writes evidence-backed reports to a temporary directory with per-item permalinks for auditing.
  • Enforces a strict read-only policy: no comments, merges, or state changes on GitHub.

Quick Start

Analyze all open issues and PRs; reports for each item will be generated in your temporary report directory.

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 open issues and PRs?

To automate GitHub triage, this Skill analyzes open issues and PRs by creating a background quick subagent per item, generating evidence-backed reports with permalinks without mutating GitHub state.

Can I analyze GitHub issues without modifying repository state?

Yes, you can analyze GitHub issues without modifying repository state because this Skill enforces a strict read-only policy, ensuring no comments, merges, or state changes occur on GitHub.

How do I triage a large repository with many open GitHub items?

Triage a large repository by running this Skill, which assigns one background quick subagent to each open item, enabling scalable analysis and generating individual reports in a temporary directory.

How are GitHub triage reports stored for auditing?

GitHub triage reports are stored for auditing by writing evidence-backed findings to a writable temporary directory, with each report including specific GitHub permalinks for the analyzed item.

Does automated GitHub triage support adding comments or merging PRs?

Automated GitHub triage does not support adding comments or merging PRs; it is strictly read-only and only generates analysis reports, preventing any mutations to the GitHub repository state.