triage-issue-local

Guide routing, labeling, and owner assignment for warp-external issues.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Repo-specific triage guidance for warp-external augments the core triage-issue rules by specializing the override categories that are marked overridable.

Core Features & Use Cases

  • Companion to core triage-issue skill, focusing on repository-specific overridable categories.
  • Ensures consistent triage decisions by applying repository context, privacy considerations, and labeling guidance.
  • Guides issue routing and owner assignment for warp-external repositories within the Warp project.

Quick Start

Load this skill to guide triage decisions for warp-external repository 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 issues in the warp-external repository?

Triage warp-external issues by applying repo-specific guidance that enforces the two-follow-up-question limit and routes issues using the repository's label taxonomy for correct owner assignment.

What is the two-follow-up-question limit for issue triage?

The two-follow-up-question limit is a triage constraint enforced within the warp-external repository to control issue routing, ensuring maintainers do not exceed two clarification questions before assignment.

How do I assign owners to warp-external issues using label taxonomy?

Assign owners to warp-external issues by applying the repository's specific label taxonomy, which guides correct routing and owner assignment across local triage contexts.

Does this triage guidance work with core triage rules?

Yes, this guidance acts as a companion to core triage rules, specializing overridable categories by applying warp-external repository context, privacy considerations, and labeling guidance.

When do I need repo-specific triage guidance for issue routing?

You need repo-specific triage guidance when processing warp-external issues that require specialized override categories, privacy considerations, and consistent labeling beyond general triage rules.

Limitations of using repository-specific triage rules for issue routing?

The primary limitation is scope: this guidance is strictly tailored for the warp-external repository and cannot be applied to triage decisions in other project repositories.