github-triage
Read-only GitHub triage for issues AND PRs. 1 item = 1 background task (category: quick). Analyzes all open items and writes evidence-backed reports to /tmp/{datetime}/. Every claim requires a GitHub permalink as proof. NEVER takes any action on GitHub - no comments, no merges, no closes, no labels. Reports only. Triggers: 'triage', 'triage issues', 'triage PRs', 'github triage'.
Best for Project maintainersWorks with GitHubLow risk
⌘source
- author
@code-yeongyu- language
- TypeScript
★53kstars
4.2kforks
Apr 18, 2026
✦overview.md
Key Features
- ·Read-only GitHub analysis for issues and PRs
- ·Spawns one background subagent per item
- ·Writes evidence-backed reports to local files
- ·Never takes any action on GitHub
- ·Analyzes all open items simultaneously
Use Cases
- →Systematically reviewing all open GitHub issues for a project
- →Analyzing pull requests before a team meeting
- →Generating status reports on open items without manual review
- →Auditing issue and PR backlog for triage prioritization
Best for
- ✓Project maintainers
- ✓Team leads needing backlog overviews
- ✓Release planning sessions
Not ideal for
- !Automating GitHub workflows
- !Direct issue management
- !Real-time notifications
FAQs
name
github-triage
description
Read-only GitHub triage for issues AND PRs. 1 item = 1 background task (category: quick). Analyzes all open items and writes evidence-backed reports to /tmp/{datetime}/. Every claim requires a GitHub permalink as proof. NEVER takes any action on GitHub - no comments, no merges, no closes, no labels. Reports only. Triggers: 'triage', 'triage issues', 'triage PRs', 'github triage'.
GitHub Triage - Read-Only Analyzer
<role> Read-only GitHub triage orchestrator. Fetch open issues/PRs, classify, spawn 1 background `quick` subagent per item. Each subagent analyzes and writes a report file. ZERO GitHub mutations. </role>Architecture
1 ISSUE/PR = 1 task_create = 1 quick SUBAGENT (background). NO EXCEPTIONS.
| Rule | Value |
|---|---|
| Category | quick |
| Execution | run_in_background=true |
| Parallelism | ALL items simultaneously |
| Tracking | task_create per item |
| Output | /tmp/{YYYYMMDD-HHmmss}/issue-{N}.md or pr-{N}.md |
Zero-Action Policy (ABSOLUTE)
<zero_action> Subagents MUST NEVER run ANY command that writes or mutates GitHub state.
FORBIDDEN (non-exhaustive):
gh issue comment, gh issue close, gh issue edit, gh pr comment, gh pr merge, gh pr review, gh pr edit, gh api -X POST, gh api -X PUT, gh api -X PATCH, gh api -X DELETE
ALLOWED:
gh issue view,gh pr view,gh api(GET only) - read GitHub dataGrep,Read,Glob- read codebaseWrite- write report files to/tmp/ONLYgit log,git show,git blame- read git history (for finding fix commits)
$install
1-click copynpx skills add code-yeongyu/oh-my-openagent --skill github-triageSafety assessment
★
Clarity score
How clear and easy to understand the SKILL.md instructions are, rated from 1 to 5.
5/ 5
excellentVery clear and well structured, with almost no room for misunderstanding.
◎
Actionability score
How directly an agent can act on the SKILL.md instructions, rated from 1 to 5.
5/ 5
very highHighly actionable with clear, concrete steps that an agent can follow directly.