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'.
Profile →npx skills add code-yeongyu/oh-my-openagent --skill github-triage --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 data - `Grep`, `Read`, `Glob` - read codebase - `Write` - write report files to `/tmp/` ONLY - `git log`, `git show`, `git blame` - read git history (for finding fix commits) **ANY GitHub
- Architecture
- Zero-Action Policy (ABSOLUTE)
- Evidence Rule (MANDATORY)
- How to generate permalinks
- Rules
- Phase 0: Setup
- Phase 1: Fetch All Open Items (CORRECTED)
- Phase 2: Classify
- Phase 3: Spawn Subagents (Individual Tool Calls)
- Step 3.1: Create Task Record
- Step 3.2: Spawn Analysis Subagent (Background)
- Subagent Prompts
- Common Preamble (include in ALL subagent prompts)
- ISSUEQUESTION
mkdir -p "$REPORT_DIR" Step 1: Fetch basic metadata (without body/comments to avoid JSON parsing issues) Paginate if needed if [ "$ISSUE_COUNT" -eq 500 ]; then while true; do done fi Same for PRs if [ "$PR_COUNT" -eq 500 ]; then echo "Total issues: $ISSUE_COUNT, Total PRs: $PR_COUNT"
What does the github-triage skill do?
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'.
How do I install it?
Run `npx skills add code-yeongyu/oh-my-openagent --skill github-triage --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From code-yeongyu/oh-my-openagent, a repository with 67,209 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.