triage-issue-local
starsforks
How to install triage-issue-local?
warpdotdev/oz-for-oss/triage-issue-local
$npx -y skills add warpdotdev/oz-for-oss --skill triage-issue-localRepo-specific triage guidance for oz-for-oss. Only the categories declared overridable by the core triage-issue skill may be specialized here.
SKILL.md
| 1 | # Repo-specific triage guidance for `oz-for-oss` |
| 2 | |
| 3 | This file is a companion to the core `triage-issue` skill. It does not |
| 4 | redefine the triage output schema, safety rules, or follow-up-question |
| 5 | contract. It only specializes the override categories the core skill |
| 6 | marks as overridable. |
| 7 | |
| 8 | ## Heuristics |
| 9 | |
| 10 | - Distinguish observed symptoms from reporter hypotheses and proposed fixes. |
| 11 | - 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. |
| 12 | - Ask targeted follow-up questions only for details the agent cannot derive itself and that materially improve triage confidence. |
| 13 | - Prefer issue-specific questions over generic "please share more info" requests. |
| 14 | |
| 15 | ## Label taxonomy |
| 16 | |
| 17 | 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. |
| 18 | |
| 19 | `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. |
| 20 | |
| 21 | ## Recurring follow-up patterns |
| 22 | |
| 23 | 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. |
| 24 | |
| 25 | ## Owner-inference hints |
| 26 | |
| 27 | No repo-specific owner-inference hints beyond `.github/STAKEHOLDERS` have been captured yet. |
People who liked this also viewed
6 picksType
- find-skillsHelps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skSkillsJul 2026
- grill-meA relentless interview to sharpen a plan or design.SkillsJul 2026
- vercel-react-best-practicesVercel's official collection of agent skillsSkillsJul 2026
- improve-codebase-architectureScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.SkillsJul 2026
- setup-matt-pocock-skillsConfigure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.SkillsJul 2026
- triageMove issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.SkillsJul 2026
