triage-issue-local

Provide triage guidance for public Warp client repository issues.

30|4|Updated May 3, 2026

Search Tags:#issue triage #sensitive information #public repository #triage guidance #Warp client

Ready to run

npx skills add https://github.com/OniroHuaver/openwarp --skill triage-issue-local-onirohuaver

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: triage-issue-local
Source: https://github.com/OniroHuaver/openwarp/tree/main/.agents/skills/triage-issue-local
Command: npx skills add https://github.com/OniroHuaver/openwarp --skill triage-issue-local-onirohuaver

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides specialized triage guidance for issues reported against the public Warp client repository, focusing on public-facing guidance to avoid sensitive information and improve issue handling.

Core Features & Use Cases

Specialized Triage Guidance: Offers repository-specific instructions for triaging issues to avoid sensitive information disclosure.
Heuristics: Includes guidelines for handling reports related to billing, appeals, and general public issue reporting.
Label Taxonomy: Provides a structured approach to issue labeling, including area-specific labels based on reported surfaces.
Follow-up Questions: Outlines best practices for follow-up questions, ensuring high-value and meaningful responses.
Owner Inference Hints: Offers guidelines for inferring the appropriate owner for issues, based on .github/STAKEHOLDERS or labels/issue surfaces.

Quick Start

Run the 'triage-issue-local' skill to get repository-specific triage guidance for an issue report.

Frequently Asked Questions about triage-issue-local

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I triage public repository issues without exposing sensitive information?▼

Triage issues safely by applying repository-specific guidance that prevents sensitive information disclosure. This approach provides public-facing heuristics and follow-up question guidelines to handle issue reports securely.

What is the best way to label issues reported against a public Warp client repository?▼

Label issues using a structured label taxonomy that applies area-specific labels based on reported surfaces. This taxonomy ensures consistent categorization for public Warp client repository issues.

How do I infer the appropriate owner for a public issue report?▼

Infer issue ownership by checking the .github/STAKEHOLDERS file or mapping issue surfaces and labels to specific teams. These guidelines help route public repository issues to the correct maintainers.

How should I handle billing and appeal reports in a public GitHub repository?▼

Handle billing and appeal reports using specialized heuristics designed for public-facing issue triage. These guidelines ensure sensitive cases are managed appropriately without public data exposure.

What are the best follow-up questions for triaging public issue reports?▼

Ask high-value follow-up questions by following outlined best practices for issue triage. These guidelines ensure meaningful responses and improve issue handling for the public Warp client repository.