triage-issue

Analyze GitHub issues to classify type, estimate reproducibility, and propose root causes.

292|39|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/warpdotdev/oz-for-oss --skill triage-issue-warpdotdev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage-issue
Source: https://github.com/warpdotdev/oz-for-oss/tree/main/.agents/skills/triage-issue
Command: npx skills add https://github.com/warpdotdev/oz-for-oss --skill triage-issue-warpdotdev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Triage a newly filed GitHub issue in this repository by analyzing the report, inspecting relevant code, estimating reproducibility, suggesting the likely root cause, and returning structured triage output without mutating GitHub directly.

Core Features & Use Cases

  • Classify issue type (bug, enhancement, documentation)
  • Inspect code references and repository context to estimate reproducibility
  • Propose root cause and prepare structured triage output
  • Generate actionable follow-up questions or identify duplicates to facilitate resolution

Quick Start

Provide the issue text and context to triage and return a structured triage output.

Frequently Asked Questions about triage-issue

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

FAQPage Schema
How do I automate GitHub issue triage for my repository?

Automate GitHub issue triage by analyzing report text, inspecting relevant code, and evaluating repository context to classify issues, estimate reproducibility, and propose root causes without mutating GitHub directly.

How does automated issue triage determine if a bug is reproducible?

Automated issue triage estimates reproducibility by inspecting code references and repository context mentioned in the report, cross-referencing the described behavior against actual codebase logic to validate the claim.

Can I classify GitHub issues as bugs, enhancements, or documentation automatically?

Yes, you can classify GitHub issues automatically by evaluating the issue content against repository conventions to determine if it is a bug, enhancement, or documentation request, returning structured triage metadata.

How do I identify duplicate GitHub issues and generate follow-up questions?

Identify duplicate GitHub issues and generate follow-up questions by analyzing the report and repository context to spot existing similar reports and formulate actionable questions needed to facilitate resolution.

Does the triage output modify GitHub issues directly or require manual review?

The triage output does not modify GitHub directly, requiring manual review. It treats issue content as untrusted unless explicitly marked as trusted and outputs structured metadata including labels and proposed root causes.