agentleFS
Sign inStart free
warpdotdevwarpdotdev/oz-for-oss/.agents/skills/triage-issue-local/SKILL.md

triage-issue-local

Skill313 starsChanged 6 months agoMITView on GitHub

Repo-specific triage guidance for oz-for-oss. Only the categories declared overridable by the core triage-issue skill may be specialized here.

6 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use classify-changelog-pr, cross-platform-cloud-verification and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • black12-agSkill

    classify-changelog-pr

    Reference guidance for classifying whether an unmarked PR should appear in the changelog and under which category. Used inline by the changelog-draft skill — not dispatched as a separate agent.

    Also in 4 projects that use this

  • black12-agSkill

    cross-platform-cloud-verification

    Orchestrates cost-conscious cloud verification across available operating-system and architecture runners after cheaper checks pass. Use whenever a code change, bug fix, build, packaging flow, native dependency, UI behavior, filesystem behavior, or test has material cross-platform implications, even if the user only asks to verify or test the change. Consult domain verification skills for what to test; use this skill to choose and access the smallest relevant set of platforms.

    Also in 4 projects that use this

  • +10 more from black12-ag

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before asking any follow-up question, first try to answer it yourself through code inspection, documentation lookup, or web search.

    line 17
  2. Distinctive:

    Ask targeted follow-up questions only for details the agent cannot derive itself and that materially improve triage confidence.

    line 18
  3. Distinctive:

    Prefer issue-specific questions over generic "please share more info" requests.

    line 19
  4. Very specific:

    No repo-specific owner-inference hints beyond .github/STAKEHOLDERS have been captured yet.

    line 33

“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free