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.
Warp-specific triage heuristics for public issue reports: protect private details, separate observed behavior from guesses and check existing features before asking questions.
Install Warp Issue Triage Heuristics
$ npx skills add warpdotdev/oz-for-oss --skill triage-issue-local -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install warpdotdev/oz-for-oss triage-issue-local --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/warpdotdev/oz-for-oss.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/triage-issue-local .claude/skills/triage-issue-local && 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 "triage-issue-local" agent skill from https://github.com/warpdotdev/oz-for-oss/tree/main/.agents/skills/triage-issue-local into .claude/skills/triage-issue-local/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "triage-issue-local", 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/warpdotdev/oz-for-oss/tree/main/.agents/skills/triage-issue-localType 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 warpdotdev/oz-for-oss --skill triage-issue-local -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install warpdotdev/oz-for-oss triage-issue-local --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/warpdotdev/oz-for-oss.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/triage-issue-local .agents/skills/triage-issue-local && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "triage-issue-local" agent skill from https://github.com/warpdotdev/oz-for-oss/tree/main/.agents/skills/triage-issue-local into .agents/skills/triage-issue-local/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "triage-issue-local", 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 warpdotdev/oz-for-oss --skill triage-issue-local -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install warpdotdev/oz-for-oss triage-issue-local --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/warpdotdev/oz-for-oss.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/triage-issue-local .cursor/skills/triage-issue-local && 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 "triage-issue-local" agent skill from https://github.com/warpdotdev/oz-for-oss/tree/main/.agents/skills/triage-issue-local into .cursor/skills/triage-issue-local/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "triage-issue-local", 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/warpdotdev/oz-for-oss.git --path .agents/skills/triage-issue-local--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 warpdotdev/oz-for-oss --skill triage-issue-local -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install warpdotdev/oz-for-oss triage-issue-local --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/warpdotdev/oz-for-oss.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/triage-issue-local .gemini/skills/triage-issue-local && 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 "triage-issue-local" agent skill from https://github.com/warpdotdev/oz-for-oss/tree/main/.agents/skills/triage-issue-local into .gemini/skills/triage-issue-local/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "triage-issue-local", 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 warpdotdev/oz-for-oss triage-issue-localInstalls 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 warpdotdev/oz-for-oss --skill triage-issue-local -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/warpdotdev/oz-for-oss.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/triage-issue-local .github/skills/triage-issue-local && 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 "triage-issue-local" agent skill from https://github.com/warpdotdev/oz-for-oss/tree/main/.agents/skills/triage-issue-local into .github/skills/triage-issue-local/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "triage-issue-local", 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 warpdotdev/oz-for-oss --skill triage-issue-local -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install warpdotdev/oz-for-oss triage-issue-local --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/warpdotdev/oz-for-oss.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/triage-issue-local .opencode/skills/triage-issue-local && 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 "triage-issue-local" agent skill from https://github.com/warpdotdev/oz-for-oss/tree/main/.agents/skills/triage-issue-local into .opencode/skills/triage-issue-local/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "triage-issue-local", 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
triage-issue-local- GitHub stars
- 313
- Token cost
- ~603 tokens
- SKILL.md length
- 294 words
- Files
- 1
- Skills in repo
- 17
- Repo updated
- First seen
- Licence
- MIT
At a glance
Warp-specific triage heuristics for public issue reports: protect private details, separate observed behavior from guesses and check existing features before asking questions.
- Triaging a new issue on the public warp repository
- SKILL.md covers Heuristics, Label taxonomy, Recurring follow-up patterns and Owner-inference hints
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Deciding whether a reported problem is specific to Warp or reproducible elsewhere
What it does
This companion to the core `triage-issue` skill adds heuristics for the public repository of the Warp desktop client. It is not usable alone: the agent checks that the parent skill is present and copies it from the declared source if it is missing. The parent keeps ownership of the triage output schema, the safety rules and the follow-up question contract.
Public reports are treated as possibly incomplete, and the agent never asks for secrets, tokens, private workspace or repository names or account identifiers in a public thread. It separates what the reporter saw from their guesses about Rust modules or product intent, and when another terminal, editor or shell is involved it decides whether the problem is specific to Warp. Screenshots, videos, logs and stack traces count as primary evidence, and the docs and existing features are checked first, so a request already met by a setting gets that setting as the answer.
When your agent uses it
- Triaging a new issue on the public warp repository
- Deciding whether a reported problem is specific to Warp or reproducible elsewhere
- Writing follow-up questions that do not ask for private details
- Pointing a reporter to an existing feature that already covers the request
Example prompts
- “Triage this new warp issue and tell me what information is still missing.”
- “The reporter says tmux breaks scrolling. Is that Warp-specific or does it happen elsewhere too?”
- “Draft follow-up questions for this report without asking for tokens or private names.”
Requirements
- The parent triage-issue skill installed under .agents/skills
What it can do on your machine
Read from SKILL.md and the folder at commit a2bb45f. 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
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
Warp Issue Triage Heuristics loads about 603 tokens when it runs. Until then it costs about 40 tokens; SKILL.md has 294 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 warpdotdev/oz-for-oss at commit a2bb45f, republished under its MIT licence (© warpdotdev). 294 words, ~603 tokens.
Download SKILL.mdSave it as
.claude/skills/triage-issue-local/SKILL.md (or your agent's skills folder).- name
- triage-issue-local
- description
- Repo-specific triage guidance for oz-for-oss. Only the categories declared overridable by the core triage-issue skill may be specialized here.
- specializes
- triage-issue
Repo-specific triage guidance for oz-for-oss
This file is a companion to the core triage-issue skill. It does not
redefine the triage output schema, safety rules, or follow-up-question
contract. It only specializes the override categories the core skill
marks as overridable.
Heuristics
- Distinguish observed symptoms from reporter hypotheses and proposed fixes.
- Before asking any follow-up question, first try to answer it yourself through code inspection, documentation lookup, or web search. Only ask questions that you cannot resolve on your own and that only the reporter would know.
- Ask targeted follow-up questions only for details the agent cannot derive itself and that materially improve triage confidence.
- Prefer issue-specific questions over generic "please share more info" requests.
Label taxonomy
The label taxonomy for this repository is managed in .github/issue-triage/config.json. Prefer labels from that configuration, and avoid inventing new labels unless the prompt explicitly allows it.
warp:needs-support is a configured label for issues that cannot be resolved through OSS contributions (billing inquiries, plan changes, refund requests, subscription or account management, pricing questions, payment issues). When you triage such a report, request warp:needs-support, set close_issue to true, and direct the reporter to Warp support in statements; the workflow applies the label, posts the support-escalation comment, and closes the issue. Do not use this label or close_issue for issues that can be addressed via OSS contributions.
Recurring follow-up patterns
No repo-specific follow-up patterns have been captured for this repository yet. oz-for-oss is not a terminal or desktop application, so the GPU/driver, window-manager, shell-integration, and similar runtime-environment sub-items that only make sense for those products do not belong here. The weekly update-triage loop will propose additions as maintainer overrides reveal recurring patterns that are actually specific to this repository.
Owner-inference hints
No repo-specific owner-inference hints beyond .github/STAKEHOLDERS have been captured yet.
© warpdotdev, 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 .agents/skills/triage-issue-local of warpdotdev/oz-for-oss.
Open the folder on GitHubat commit a2bb45f
Compare with similar skills
Warp Issue Triage Heuristics 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 |
|---|---|---|---|---|---|---|
| Warp Issue Triage Heuristics this skillwarpdotdev/oz-for-oss | 313 | — | ~603 | Automated safety check: Pass | MIT | |
| Pre-Release PR Triagejamiepine/voicebox | 57k | — | ~3.1k | Automated safety check: Pass | MIT | |
| WinAppSDK Triage Meeting Prepmicrosoft/WindowsAppSDK | 4.7k | — | ~2.8k | Automated safety check: Pass | Apache-2.0 | |
| Ouroboros Maintainer TriageQ00/ouroboros | 6.2k | — | ~1.7k | Automated safety check: Pass | MIT | |
| RTK Issue Triagertk-ai/rtk | 83k | — | ~3k | Automated safety check: Notes | Apache-2.0 | |
| Verdaccio Issue Triageverdaccio/verdaccio | 18k | — | ~2.4k | Automated safety check: Pass | MIT |
Similar skills
- Official
WinAppSDK Triage Meeting Prep
microsoft/WindowsAppSDK
Prepares the triage meeting summary for WinAppSDK Needs-Triage issues, with research-backed area suggestions, draft replies and a diff since the last triage.
Ouroboros Maintainer Triage
Q00/ouroboros
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.
RTK Issue Triage
rtk-ai/rtk
Audits open GitHub issues, categorizes them, flags duplicates and linked PRs in three phases, with optional deep analysis and comments posted only after validation.
Verdaccio Issue Triage
verdaccio/verdaccio
Triages an incoming verdaccio/verdaccio issue against the code, the affected release line and related issues, and picks labels from the repository's existing taxonomy.
Issue and PR Triage
stickerdaniel/linkedin-mcp-server
Turns the open issues and pull requests of the linkedin-mcp-server repository into a read-only priority list for maintainers.
More from warpdotdev/oz-for-oss
All 17 skills in this repoUpdate Dedupe
warpdotdev/oz-for-oss
Update the repo-local dedupe-issue-local companion skill using closed-as-duplicate signals.
Update PR Review
warpdotdev/oz-for-oss
Update the repo-local review-pr-local and review-spec-local companion skills using human feedback left on pull request conversations.
Bootstrap Issue Config
warpdotdev/oz-for-oss
Bootstrap the issue triage configuration for a repository by analyzing existing issues, labels, and contributors to generate .github/issue-triage/config.json and .github/STAKEHOLDERS.
Update Triage
warpdotdev/oz-for-oss
Update the repo-local triage-issue-local companion skill using signals from recently triaged issues (maintainer re-labels, re-opens, follow-up comments).
Implement Issue
warpdotdev/oz-for-oss
Implement a GitHub issue in this repository by applying the shared implement-specs workflow with Oz-specific issue, spec-context, and summary-file handling.
Review Spec
warpdotdev/oz-for-oss
Review a spec/plan pull request diff and write structured feedback to review.json for the workflow to publish.
Related
Categories
Questions about Warp Issue Triage Heuristics
What does Warp Issue Triage Heuristics do?
Warp-specific triage heuristics for public issue reports: protect private details, separate observed behavior from guesses and check existing features before asking questions. This companion to the core `triage-issue` skill adds heuristics for the public repository of the Warp desktop client. It is not usable alone: the agent checks that the parent skill is present and copies it from the declared source if it is missing.
When should I use Warp Issue Triage Heuristics?
Warp Issue Triage Heuristics fits situations like: triaging a new issue on the public warp repository; deciding whether a reported problem is specific to Warp or reproducible elsewhere; writing follow-up questions that do not ask for private details; pointing a reporter to an existing feature that already covers the request.
How do I install Warp Issue Triage Heuristics in Claude Code?
Run `npx skills add warpdotdev/oz-for-oss --skill triage-issue-local -a claude-code`. Or copy the skill folder (.agents/skills/triage-issue-local in warpdotdev/oz-for-oss) into .claude/skills/triage-issue-local in your project. Claude Code loads it when a task matches its description.
How do I install Warp Issue Triage Heuristics in Codex?
Run `npx skills add warpdotdev/oz-for-oss --skill triage-issue-local -a codex`. Or copy the skill folder (.agents/skills/triage-issue-local in warpdotdev/oz-for-oss) into .agents/skills/triage-issue-local in your project. Codex loads it when a task matches its description.
Can I use Warp Issue Triage Heuristics 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 warpdotdev/oz-for-oss --skill triage-issue-local -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/triage-issue-local, .gemini/skills/triage-issue-local, .github/skills/triage-issue-local and .opencode/skills/triage-issue-local in your project.
What does Warp Issue Triage Heuristics need to run?
SKILL.md names no scripts, command-line tools or credentials: Warp Issue Triage Heuristics is instructions for the agent only. Our summary lists: The parent triage-issue skill installed under .agents/skills.
Does Warp Issue Triage Heuristics access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Warp Issue Triage Heuristics 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 Warp Issue Triage Heuristics use?
Warp Issue Triage Heuristics 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 Warp Issue Triage Heuristics use?
About 603 tokens (SKILL.md is roughly 2.4k 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 Warp Issue Triage Heuristics?
Skills that share tags, products or a category with Warp Issue Triage Heuristics: Pre-Release PR Triage (jamiepine/voicebox, 57k stars), WinAppSDK Triage Meeting Prep (microsoft/WindowsAppSDK, 4.7k stars), Ouroboros Maintainer Triage (Q00/ouroboros, 6.2k stars) and RTK Issue Triage (rtk-ai/rtk, 83k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Warp Issue Triage Heuristics?
warpdotdev (a GitHub organization) maintains it in warpdotdev/oz-for-oss, which has 313 GitHub stars. The repository holds 17 skills in this directory. The repository was last updated on September 17, 2026.
Source: warpdotdev/oz-for-oss on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.