Pre-Release PR Triage
jamiepine/voicebox
Sorts a backlog of open pull requests into must-merge, candidate, superseded and deferred, writes a triage doc and works the merge loop before a release.
Fans out one background subagent per open GitHub issue or pull request to write an evidence-backed report, never commenting, closing or merging anything.
Install Read-Only GitHub Triage
$ npx skills add code-yeongyu/oh-my-openagent --skill github-triage -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install code-yeongyu/oh-my-openagent github-triage --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/code-yeongyu/oh-my-openagent.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/github-triage .claude/skills/github-triage && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "github-triage" agent skill from https://github.com/code-yeongyu/oh-my-openagent/tree/dev/.agents/skills/github-triage into .claude/skills/github-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-triage", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/code-yeongyu/oh-my-openagent/tree/dev/.agents/skills/github-triageType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add code-yeongyu/oh-my-openagent --skill github-triage -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install code-yeongyu/oh-my-openagent github-triage --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/code-yeongyu/oh-my-openagent.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/github-triage .agents/skills/github-triage && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "github-triage" agent skill from https://github.com/code-yeongyu/oh-my-openagent/tree/dev/.agents/skills/github-triage into .agents/skills/github-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-triage", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add code-yeongyu/oh-my-openagent --skill github-triage -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install code-yeongyu/oh-my-openagent github-triage --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/code-yeongyu/oh-my-openagent.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/github-triage .cursor/skills/github-triage && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "github-triage" agent skill from https://github.com/code-yeongyu/oh-my-openagent/tree/dev/.agents/skills/github-triage into .cursor/skills/github-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-triage", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/code-yeongyu/oh-my-openagent.git --path .agents/skills/github-triage--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add code-yeongyu/oh-my-openagent --skill github-triage -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install code-yeongyu/oh-my-openagent github-triage --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/code-yeongyu/oh-my-openagent.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/github-triage .gemini/skills/github-triage && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "github-triage" agent skill from https://github.com/code-yeongyu/oh-my-openagent/tree/dev/.agents/skills/github-triage into .gemini/skills/github-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-triage", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install code-yeongyu/oh-my-openagent github-triageInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add code-yeongyu/oh-my-openagent --skill github-triage -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/code-yeongyu/oh-my-openagent.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/github-triage .github/skills/github-triage && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "github-triage" agent skill from https://github.com/code-yeongyu/oh-my-openagent/tree/dev/.agents/skills/github-triage into .github/skills/github-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-triage", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add code-yeongyu/oh-my-openagent --skill github-triage -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install code-yeongyu/oh-my-openagent github-triage --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/code-yeongyu/oh-my-openagent.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/github-triage .opencode/skills/github-triage && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "github-triage" agent skill from https://github.com/code-yeongyu/oh-my-openagent/tree/dev/.agents/skills/github-triage into .opencode/skills/github-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-triage", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
github-triage- GitHub stars
- 70k
- Token cost
- ~4.3k tokens
- SKILL.md length
- 623 words
- Files
- 2 (incl. scripts)
- Skills in repo
- 44
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Fans out one background subagent per open GitHub issue or pull request to write an evidence-backed report, never commenting, closing or merging anything.
- Works in 6 steps: Setup → Fetch All Open Items (CORRECTED) → Classify → …
- Getting an evidence-backed report on every open issue in a repository
- SKILL.md covers Architecture, Zero-Action Policy (ABSOLUTE), Evidence Rule (MANDATORY) and Phase 0: Setup, plus 7 more sections
- Runs Python scripts from its folder; calls gh, jq and git; reaches github.com
What it does
Fetches every open issue and pull request, classifies them, and spawns exactly one quick background subagent per item running in parallel, tracked with a task-creation call per item, writing each result to its own timestamped report file rather than acting on GitHub directly. Any GitHub-mutating command, such as commenting, closing, editing, merging or a non-GET API call, is an explicitly forbidden, critical violation; only read commands like viewing an issue or PR, GET API calls, and local codebase or git-history reads are allowed.
Every factual claim in a report must carry a GitHub permalink pointing to a specific line range in a specific commit SHA as proof, built by finding the file and line with a search, grabbing the current commit SHA, and constructing the blob URL from both; a permalink to a branch name like main is not acceptable, only a commit SHA. A claim with no permalink is either dropped in favor of stating that no evidence was found, or explicitly marked as unverified and given no weight in the report.
A fixed setup phase resolves the repository name and creates a timestamped report directory before any subagent work begins, and that repository name, directory and commit SHA are passed to every spawned subagent so each one builds consistent permalinks.
When your agent uses it
- Getting an evidence-backed report on every open issue in a repository
- Triaging a backlog of pull requests without taking any action on them
- Finding which open issues already have a fix commit in git history
- Auditing claims about a bug by checking they carry a real commit permalink
Example prompts
- “Triage all our open issues and write a report for each one.”
- “Triage PRs — I just want the analysis, don't comment on anything.”
- “Which of these open issues already have a fix sitting in git history?”
Requirements
- The gh CLI
- Python, to run the bundled fetch script
Workflow steps
6 steps, taken from the step headings in SKILL.md.
- Setup
- Fetch All Open Items (CORRECTED)
- Classify
- Spawn Subagents (Individual Tool Calls)
- Collect & Update
- Final Summary
What it can do on your machine
Read from SKILL.md and the folder at commit cbd7dd2. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
ghjqgit
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
github.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Read-Only GitHub Triage loads about 4.3k tokens when it runs. Until then it costs about 99 tokens; SKILL.md has 623 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 623 words (~4,280 tokens).
“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.”
- name
- github-triage
Files
SKILL.md and 1 other file (scripts) in .agents/skills/github-triage of code-yeongyu/oh-my-openagent.
- SKILL.md
- scripts/gh_fetch.py
Open the folder on GitHubat commit cbd7dd2
Compare with similar skills
Read-Only GitHub Triage next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Read-Only GitHub Triage this skillcode-yeongyu/oh-my-openagent | 70k | — | ~4.3k | Automated safety check: Pass | Custom licence | |
| Pre-Release PR Triagejamiepine/voicebox | 57k | — | ~3.1k | Automated safety check: Pass | MIT | |
| PR Triagertk-ai/rtk | 83k | — | ~2.5k | Automated safety check: Notes | Apache-2.0 | |
| GitHub Triagetrailofbits/skills | 7.4k | — | ~5.8k | Automated safety check: Notes | CC-BY-SA-4.0 | |
| Contributor-First PR MergeHKUDS/OpenHarness | 16k | 1 repos | ~847 | Automated safety check: Pass | MIT | |
| Create Pull Requestcline/cline | 70k | 1 repos | ~1.6k | Automated safety check: Pass | Apache-2.0 |
Similar skills
PR Triage
rtk-ai/rtk
Audits a repository's open pull requests, deep-reviews chosen ones and drafts review comments that are only posted after you approve them.
- Official
GitHub Triage
trailofbits/skills
Triages open GitHub issues and pull requests with the gh CLI, optionally merging ready PRs, closing resolved issues with evidence and assigning local priority and size estimates.
Contributor-First PR Merge
HKUDS/OpenHarness
Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.
Create Pull Request
cline/cline
Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.
Pull Request Title and Body Writer
openinterpreter/openinterpreter
Rewrites the title and body of one or more pull requests with gh, leading with why the change was made, then what changed, and describing only the net result.
More from code-yeongyu/oh-my-openagent
All 44 skills in this repoast-grep Structural Search
code-yeongyu/oh-my-openagent
Searches and rewrites code by syntax-tree shape across 25 languages with ast-grep, for codemods, structural queries and YAML lint rules, using a Python wrapper script.
Browser Control with Omowright
code-yeongyu/oh-my-openagent
Drives a real browser through the omowright library, either the user's own signed-in browser or a separate browser the code launches, for forms, QA, screenshots and scraping.
Codex Plugin QA
code-yeongyu/oh-my-openagent
Tests the omo Codex plugin in an isolated CODEX_HOME with a local mock model, proving hooks fired through app-server notifications without touching ~/.codex.
Coding Agent Session Finder
code-yeongyu/oh-my-openagent
Finds, reads and reconstructs past coding-agent sessions across Codex, Claude, OpenCode, Senpi and many other local agent logs.
LSP Setup
code-yeongyu/oh-my-openagent
Detects which languages a project uses, installs the matching language server, writes its config and checks it with a real call so diagnostics and go-to-definition work.
OpenCode QA Toolkit
code-yeongyu/oh-my-openagent
Tests the opencode coding agent itself: its CLI, server, plugin hooks and events, the terminal UI under tmux, and its SQLite session database, using tested helper scripts.
Related
Categories
Questions about Read-Only GitHub Triage
What does Read-Only GitHub Triage do?
Fans out one background subagent per open GitHub issue or pull request to write an evidence-backed report, never commenting, closing or merging anything. Fetches every open issue and pull request, classifies them, and spawns exactly one quick background subagent per item running in parallel, tracked with a task-creation call per item, writing each result to its own timestamped report file rather than acting on GitHub directly. Any GitHub-mutating command, such as commenting, closing, editing, merging or a non-GET API call, is an explicitly forbidden, critical violation; only read commands like viewing an issue or PR, GET API calls, and local codebase or git-history reads are allowed.
When should I use Read-Only GitHub Triage?
Read-Only GitHub Triage fits situations like: getting an evidence-backed report on every open issue in a repository; triaging a backlog of pull requests without taking any action on them; finding which open issues already have a fix commit in git history; auditing claims about a bug by checking they carry a real commit permalink.
How do I install Read-Only GitHub Triage in Claude Code?
Run `npx skills add code-yeongyu/oh-my-openagent --skill github-triage -a claude-code`. Or copy the skill folder (.agents/skills/github-triage in code-yeongyu/oh-my-openagent) into .claude/skills/github-triage in your project. Claude Code loads it when a task matches its description.
How do I install Read-Only GitHub Triage in Codex?
Run `npx skills add code-yeongyu/oh-my-openagent --skill github-triage -a codex`. Or copy the skill folder (.agents/skills/github-triage in code-yeongyu/oh-my-openagent) into .agents/skills/github-triage in your project. Codex loads it when a task matches its description.
Can I use Read-Only GitHub Triage in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add code-yeongyu/oh-my-openagent --skill github-triage -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/github-triage, .gemini/skills/github-triage, .github/skills/github-triage and .opencode/skills/github-triage in your project.
What does Read-Only GitHub Triage need to run?
Going by SKILL.md and its folder, Read-Only GitHub Triage needs Python for the scripts in its folder and the command-line tools its instructions call (gh, jq and git). Our summary lists: The gh CLI; Python, to run the bundled fetch script.
Does Read-Only GitHub Triage access the network?
SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Read-Only GitHub Triage safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Read-Only GitHub Triage use?
Read-Only GitHub Triage has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Read-Only GitHub Triage use?
About 4.3k tokens (SKILL.md is roughly 17k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Read-Only GitHub Triage?
Skills that share tags, products or a category with Read-Only GitHub Triage: Pre-Release PR Triage (jamiepine/voicebox, 57k stars), PR Triage (rtk-ai/rtk, 83k stars), GitHub Triage (trailofbits/skills, 7.4k stars) and Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Read-Only GitHub Triage?
code-yeongyu (a GitHub user) maintains it in code-yeongyu/oh-my-openagent, which has 69,850 GitHub stars. The repository holds 44 skills in this directory. The repository was last updated on October 7, 2026.
Source: code-yeongyu/oh-my-openagent on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.