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.
Triages and works through GitHub issues and pull requests in the Q00/ouroboros repo as a maintainer, within a stated review boundary and clear limits on what it may change.
Install Ouroboros Maintainer Triage
$ npx skills add Q00/ouroboros --skill maintain -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Q00/ouroboros maintain --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/Q00/ouroboros.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/maintain .claude/skills/maintain && 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 "maintain" agent skill from https://github.com/Q00/ouroboros/tree/main/skills/maintain into .claude/skills/maintain/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maintain", 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/Q00/ouroboros/tree/main/skills/maintainType 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 Q00/ouroboros --skill maintain -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Q00/ouroboros maintain --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Q00/ouroboros.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/maintain .agents/skills/maintain && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "maintain" agent skill from https://github.com/Q00/ouroboros/tree/main/skills/maintain into .agents/skills/maintain/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maintain", 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 Q00/ouroboros --skill maintain -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Q00/ouroboros maintain --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Q00/ouroboros.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/maintain .cursor/skills/maintain && 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 "maintain" agent skill from https://github.com/Q00/ouroboros/tree/main/skills/maintain into .cursor/skills/maintain/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maintain", 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/Q00/ouroboros.git --path skills/maintain--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 Q00/ouroboros --skill maintain -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Q00/ouroboros maintain --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Q00/ouroboros.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/maintain .gemini/skills/maintain && 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 "maintain" agent skill from https://github.com/Q00/ouroboros/tree/main/skills/maintain into .gemini/skills/maintain/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maintain", 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 Q00/ouroboros maintainInstalls 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 Q00/ouroboros --skill maintain -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Q00/ouroboros.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/maintain .github/skills/maintain && 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 "maintain" agent skill from https://github.com/Q00/ouroboros/tree/main/skills/maintain into .github/skills/maintain/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maintain", 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 Q00/ouroboros --skill maintain -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Q00/ouroboros maintain --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Q00/ouroboros.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/maintain .opencode/skills/maintain && 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 "maintain" agent skill from https://github.com/Q00/ouroboros/tree/main/skills/maintain into .opencode/skills/maintain/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maintain", 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
maintain- GitHub stars
- 6.2k
- Token cost
- ~1.7k tokens
- SKILL.md length
- 1,025 words
- Files
- 1
- Skills in repo
- 23
- Repo updated
- First seen
- Licence
- MIT
At a glance
Triages and works through GitHub issues and pull requests in the Q00/ouroboros repo as a maintainer, within a stated review boundary and clear limits on what it may change.
- Works in 5 steps: Reproducible security, user-data, and… → PRs near a decision: verify or request… → Open issues whose related PRs merged:… → …
- Working through the issue and pull request backlog of Ouroboros
- SKILL.md covers Scope and authority, Review boundary, Pick the next item and Decide one item, plus 2 more sections
- Calls gh
What it does
Run through ooo maintain, the skill picks and processes the next actionable item in Q00/ouroboros, treating issues and PRs as related but not one-to-one. It reads live GitHub state through the gh CLI and needs no Ouroboros MCP setup. A request for status or a next action stays read-only, while an instruction to process named items covers justified comments, labels, closure or merge on those items only.
Before changing anything it checks gh auth status and permissions, and it never treats a bot verdict, a label, age or a green check alone as proof of completion. Code and documentation changes happen in a clean, isolated worktree that leaves other workers' checkouts alone. The review boundary asks a PR to declare one user problem, its supported inputs and conditions, observable behavior, changed subsystems and owner, non-goals and evidence, and sends scope growth back to a maintainer or RFC discussion. Another repository follows its own maintainer rules.
When your agent uses it
- Working through the issue and pull request backlog of Ouroboros
- Judging whether a pull request is ready to merge
- Spotting duplicate PRs and deciding what to do with an issue
Example prompts
- “Run ooo maintain and tell me the next actionable item.”
- “Which open PRs in Q00/ouroboros duplicate each other?”
- “Is this Ouroboros pull request ready to merge? Check CI and the review boundary without commenting.”
Requirements
- GitHub CLI (gh) with authenticated access to Q00/ouroboros
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Reproducible security, user-data, and severe user-facing regressions.
- PRs near a decision: verify or request changes, then merge a sound fix. A completed PR may also resolve an issue.
- Open issues whose related PRs merged: compare the issue's full acceptance criteria with merged code and evidence, then close only if…
- Blocked, competing, or abandoned PRs and issues: identify the next owner/action or explain a justified closure.
- New work without a PR: confirm it is still wanted and scoped before implementation.
What it can do on your machine
Read from SKILL.md and the folder at commit 0df5b98. 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
Shell commands in SKILL.md call:
gh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.
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
Ouroboros Maintainer Triage loads about 1.7k tokens when it runs. Until then it costs about 49 tokens; SKILL.md has 1,025 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); files beside SKILL.md are not scanned.
SKILL.md
The full file from Q00/ouroboros at commit 0df5b98, republished under its MIT licence (© Q00). 1,025 words, ~1,746 tokens.
Download SKILL.mdSave it as
.claude/skills/maintain/SKILL.md (or your agent's skills folder).- name
- maintain
- description
- Triage and work through Ouroboros GitHub issues and pull requests as a maintainer. Use for `ooo maintain`, backlog cleanup, review, merge readiness, duplicate PRs, and issue disposition.
Ouroboros maintenance
Use ooo maintain to choose and process the next actionable item in Q00/ouroboros. An issue describes a problem or proposed work; a PR proposes a change. They are not one-to-one. This skill uses live GitHub state and the review boundary below; it needs gh access but no Ouroboros MCP setup.
Scope and authority
- Target
Q00/ouroboros. Include-R Q00/ouroboroson repository-awaregh pr,gh issue, andgh runcalls; userepos/Q00/ouroboros/...ongh apicalls.gh auth statusis host-scoped and does not accept-R. Resolve an issue or PR number against that repository before acting. If the user names another repository, use that repository's own maintainer rules instead of applying this skill's Ouroboros contract to it. - Match the user's requested scope. A request for status or a next action is read-only. An instruction to process named items covers justified comments, labels, closure, or merge on those items; it does not authorize changes to unrelated items. Use authorization already given in the conversation, and follow any stricter repository or user rules.
- Check
gh auth statusand current permissions before a mutation. Do not request login if authenticated read/write access already works. Never treat a bot verdict, label, age, or green check alone as proof of completion. - Work from a clean, isolated worktree for code or documentation changes. Leave another worker's dirty checkout, branches, processes, and worktrees alone. When a target checkout is available, read its
AGENTS.mdandCONTRIBUTING.md; otherwise use the bundled review boundary below. Query current CI requirements before editing or reviewing a PR.
Review boundary
Require a PR to declare one user problem; supported inputs, preconditions, and execution conditions; observable behavior and invariants; changed subsystems, data or security boundaries, and owner; non-goals; and evidence. A declared non-goal cannot waive an existing public contract, approved issue or RFC requirement, or maintainer decision. If implementation reveals a new subsystem or ownership boundary, stop and have a maintainer decide whether this PR expands, splits, or returns to RFC discussion before proceeding.
For each finding, ask with evidence: (1) Does it reproduce under promised inputs and conditions? (2) Does it violate the promised contract? (3) Does the fix need a new subsystem or owner? (4) Can the original problem be solved without that added subsystem? (5) Would splitting scope leave an immediate user-data or security risk? If 1 and 2 are yes, request changes. If 3 and 5 are yes, stop for a maintainer scope decision. If 5 is yes and no new owner is needed, request changes. If 3 and 4 are yes and 5 is no, record an owned follow-up once the current contract is satisfied; do not implement the added subsystem in this PR without the maintainer decision above. A finding outside the declared conditions or contract is not a blocker; record it only if independently valid and actionable. Severity alone does not change these outcomes.
Pick the next item
Read open issues and PRs from GitHub, including their dates, authors, labels, review decisions, head commits, checks, merge state, and links. Recheck an item's live state just before acting. Prioritize:
- Reproducible security, user-data, and severe user-facing regressions.
- PRs near a decision: verify or request changes, then merge a sound fix. A completed PR may also resolve an issue.
- Open issues whose related PRs merged: compare the issue's full acceptance criteria with merged code and evidence, then close only if complete.
- Blocked, competing, or abandoned PRs and issues: identify the next owner/action or explain a justified closure.
- New work without a PR: confirm it is still wanted and scoped before implementation.
Within a comparable group, consider age and contributor waiting time. If the user asks for oldest first, inspect in creation order; explain why an older item is deferred before moving to the next actionable one. Do not equate old with stale.
Show full SKILL.md (387 more words)Show less
Decide one item
- PR: Read its stated user problem, supported inputs, observable contract, non-goals, linked issue, diff, review comments, and tests. Check the current head against review and CI results; an earlier approval may be outdated. Apply the five-question review boundary above. Verify required checks and branch mergeability against live GitHub state. If the fix is sound and authorized, squash-merge through the protected
mainworkflow; otherwise give the contributor a concrete blocker or next step. - Competing PRs: Compare commits, diffs, and promised behavior. Shared issue numbers show overlap, not identical code. Choose by coverage, correctness, review evidence, and integration cost; preserve contributor credit in the disposition. Close only a superseded proposal within the authorized set, with a link and reason. Leave the issue open until its contract is fulfilled.
- Issue after merge:
Fixes/Closesmay auto-close on merge;Refsdoes not establish completion. Check all acceptance criteria and currentmain, including any real-environment evidence the issue requires. Record the merged PR and evidence when closing. If verification remains, keep it open with the exact missing check and an owner orneeds-humanlabel when appropriate. - Stale candidate: Look for an obsolete premise, superseding work, lost relevance, or an unanswered request for information. Ask for missing evidence when useful. Close only with a specific reason; elapsed time alone is insufficient.
After each mutation, requery the changed item and backlog count. Stop a batch at an unresolved contract, failed gate, new owner/subsystem decision, or lost authorization rather than silently widening scope.
Report
For each item, give the issue/PR link, the observed state, the evidence that matters, the action taken or exact blocker, and the next action. Keep backlog counts separate from real fixes. On bare ooo maintain, return the single best next item and why it outranks the older alternatives; do not mutate GitHub merely because the skill was invoked.
RFC #1392 State Breadcrumb Footer
Your final response MUST end with exactly one breadcrumb footer line:
◆ <current state> → next: <recommended action>Derive <current state> from live session state via ouroboros_session_status when that MCP projection is available; otherwise derive it from this skill's actual outcome. Never use a linear Step N of M footer because Ouroboros is an evolutionary loop. When the next action is genuinely a choice, list 2-3 honest options in the next: clause. The breadcrumb line must be the last line of the response.
© Q00, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/maintain of Q00/ouroboros.
Open the folder on GitHubat commit 0df5b98
Compare with similar skills
Ouroboros Maintainer 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 |
|---|---|---|---|---|---|---|
| Ouroboros Maintainer Triage this skillQ00/ouroboros | 6.2k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Pre-Release PR Triagejamiepine/voicebox | 57k | — | ~3.1k | Automated safety check: Pass | MIT | |
| Qwen Code Issue and PR TriageQwenLM/qwen-code | 28k | — | ~1.8k | Automated safety check: Pass | Apache-2.0 | |
| GitHub Project Triagesteipete/agent-scripts | 7.3k | — | ~4k | Automated safety check: Pass | MIT | |
| Open Source Maintainer Assistantslopus/happy | 24k | — | ~1.9k | Automated safety check: Pass | MIT | |
| Triage Contributor PRsprisma/orm | 48k | — | ~3.6k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Qwen Code Issue and PR Triage
QwenLM/qwen-code
Gatekeeps GitHub issues and pull requests for Qwen Code maintainers through staged static reviews that post a comment after each stage, under strict safety rules.
GitHub Project Triage
steipete/agent-scripts
Produces maintainer-facing triage cards for a project's GitHub issues and pull requests, each with its URL, risk, test state, blockers and a next action.
Open Source Maintainer Assistant
slopus/happy
Helps maintain the slopus/happy open source project by triaging issues, drafting closing comments, finding duplicates and checking fixes, with approval before anything is posted.
- Official
Triage Contributor PRs
prisma/orm
Triages open pull requests from external contributors to prisma/orm, producing a per-PR verdict with evidence, without closing, commenting on or approving anything.
- 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.
More from Q00/ouroboros
All 23 skills in this repoOuroboros PM Interview
Q00/ouroboros
Runs a guided product-manager interview that classifies each question automatically and produces a Product Requirements Document.
Brownfield Repo Scanner
Q00/ouroboros
Scans a directory for existing git repositories and worktrees, then registers and manages which ones serve as default context during interviews.
Ouroboros Three-Stage Evaluate
Q00/ouroboros
Scores an agent's finished work with a three-stage pipeline: free mechanical checks, an advisory semantic review, and an optional multi-model consensus vote.
Ouroboros Evolve Loop
Q00/ouroboros
Starts, monitors or rewinds an evolutionary development loop that refines an ontology and acceptance criteria generation by generation until it converges, using the Ouroboros MCP tools.
Ouroboros Settings Opener
Q00/ouroboros
Opens or drives the Ouroboros settings GUI, picking a browser, TUI or chat-based approach depending on whether the user can reach a browser window.
Ouroboros Command Reference
Q00/ouroboros
Reference guide to the Ouroboros commands and agents, covering interviews, seed specs, evaluation, lateral-thinking personas and the evolutionary loop.
Related
Works with
Categories
Questions about Ouroboros Maintainer Triage
What does Ouroboros Maintainer Triage do?
Triages and works through GitHub issues and pull requests in the Q00/ouroboros repo as a maintainer, within a stated review boundary and clear limits on what it may change. Run through ooo maintain, the skill picks and processes the next actionable item in Q00/ouroboros, treating issues and PRs as related but not one-to-one. It reads live GitHub state through the gh CLI and needs no Ouroboros MCP setup.
When should I use Ouroboros Maintainer Triage?
Ouroboros Maintainer Triage fits situations like: working through the issue and pull request backlog of Ouroboros; judging whether a pull request is ready to merge; spotting duplicate PRs and deciding what to do with an issue.
How do I install Ouroboros Maintainer Triage in Claude Code?
Run `npx skills add Q00/ouroboros --skill maintain -a claude-code`. Or copy the skill folder (skills/maintain in Q00/ouroboros) into .claude/skills/maintain in your project. Claude Code loads it when a task matches its description.
How do I install Ouroboros Maintainer Triage in Codex?
Run `npx skills add Q00/ouroboros --skill maintain -a codex`. Or copy the skill folder (skills/maintain in Q00/ouroboros) into .agents/skills/maintain in your project. Codex loads it when a task matches its description.
Can I use Ouroboros Maintainer 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 Q00/ouroboros --skill maintain -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/maintain, .gemini/skills/maintain, .github/skills/maintain and .opencode/skills/maintain in your project.
What does Ouroboros Maintainer Triage need to run?
Going by SKILL.md and its folder, Ouroboros Maintainer Triage needs the command-line tools its instructions call (gh). Our summary lists: GitHub CLI (gh) with authenticated access to Q00/ouroboros.
Does Ouroboros Maintainer Triage access the network?
SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Ouroboros Maintainer 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. Review the folder before installing.
What licence does Ouroboros Maintainer Triage use?
Ouroboros Maintainer Triage is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Ouroboros Maintainer Triage use?
About 1.7k tokens (SKILL.md is roughly 7k 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 Ouroboros Maintainer Triage?
Skills that share tags, products or a category with Ouroboros Maintainer Triage: Pre-Release PR Triage (jamiepine/voicebox, 57k stars), Qwen Code Issue and PR Triage (QwenLM/qwen-code, 28k stars), GitHub Project Triage (steipete/agent-scripts, 7.3k stars) and Open Source Maintainer Assistant (slopus/happy, 24k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Ouroboros Maintainer Triage?
Q00 (a GitHub user) maintains it in Q00/ouroboros, which has 6,189 GitHub stars. The repository holds 23 skills in this directory. The repository was last updated on October 6, 2026.
Source: Q00/ouroboros on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.