
Github Triage
Spins up a background subagent for every GitHub issue and PR you point it at, runs triage analysis in parallel, and dumps structured reports to timestamped files in /tmp. The architecture is refreshingly simple: one item equals one task_create call equals one quick subagent doing read-only analysis. No batching, no exceptions. It's built for speed over chat-based back and forth. If you're drowning in notifications and want snapshot context on dozens of threads without manually opening tabs, this handles the grunt work. The 60K stars on the parent repo suggest the oh-my-openagent framework has legs, and this skill leans hard into its parallel execution model.
- skills.sh installs
- 2.8K
- GitHub stars
- 70.8K
- last updated
- Aug 21, 2026
Install
$ npx -y skills add code-yeongyu/oh-my-openagent --skill github-triage --agent claude-codeInstalls into .claude/skills of the current project.
Files
GitHub Triage - Read-Only Analyzer
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.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)
Sponsors
Details
- Repository
- github.com/code-yeongyu/oh-my-openagent
- Category
- Git & Pull Requests
- First seen
- Jun 3, 2026