triage-issue-local

Specialize core triage-issue rules for labeling and routing Warp issues in warp-external.

Updated Apr 28, 2026
One-click install
npx skills add https://github.com/89jobrien/warpx --skill triage-issue-local
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage-issue-local
Source: https://github.com/89jobrien/warpx/tree/main/.agents/skills/triage-issue-local
Command: npx skills add https://github.com/89jobrien/warpx --skill triage-issue-local

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides repo-specific triage guidance for warp-external that specializes the core triage-issue rules.

Core Features & Use Cases

  • Specializes the override categories in the core triage-issue skill for warp-external.
  • Provides guidance to distinguish Warp-specific vs generic issue content and to avoid exposing sensitive data in public threads.
  • Defines routing recommendations and follow-up guidance aligned with the base safety and contract of the core triage-issue skill.

Quick Start

Apply the Warp-external triage rules in this guide to classify and route incoming issues.

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 Warp issues with repo-specific routing and labeling rules?

Triage Warp issues with repo-specific rules by applying specialized guidance that overrides base triage categories. This ensures accurate labeling, routing, and follow-up decisions for warp-external issues without altering the core safety contract.

What is the best way to customize issue triage heuristics for a specific repository?

Customize issue triage heuristics by specializing overridable categories within the core triage schema. This approach tailors routing and labeling decisions while preserving the base safety rules and follow-up contracts.

How do I route Warp-specific issues while avoiding sensitive data exposure in public threads?

Route Warp-specific issues safely by applying triage guidance that distinguishes Warp content from generic issues and prevents sensitive data exposure in public threads, aligning with base safety rules.

Can I redefine the triage schema when adding repo-specific issue routing rules?

No, you cannot redefine the triage schema or safety rules. Repo-specific triage guidance only customizes overridable categories, ensuring the base contract and follow-up mechanisms remain intact.

When do I need specialized triage rules for incoming Warp issues?

You need specialized triage rules for incoming Warp issues when you want to distinguish Warp-specific content from generic issues and require tailored routing, labeling, and follow-up decisions for the warp-external repository.