issue-triage

Classifies incoming issues and produces a structured Markdown triage artifact.

2|Updated Jun 19, 2026
One-click install
npx skills add https://github.com/andrewthetechie/andrew-skills --skill issue-triage-andrewthetechie
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-triage
Source: https://github.com/andrewthetechie/andrew-skills/tree/main/issue-triage
Command: npx skills add https://github.com/andrewthetechie/andrew-skills --skill issue-triage-andrewthetechie

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you determine whether an issue is ready for implementation, needs more information, or should be marked as not actionable, without bouncing back and forth with the reporter.

Core Features & Use Cases

  • Issue Classification: Distinguishes bugs, enhancements, mixed reports, and non-actionable items.
  • Repository-Aware Analysis: Checks project guidance, docs, code, tests, and related artifacts to validate claims.
  • Actionability Review: Identifies blocking gaps, open product questions, and concrete acceptance boundaries.
  • Output-Ready Triage: Produces a single Markdown artifact suitable for downstream posting or handoff.

Quick Start

Use the issue triage skill to analyze this issue and return a complete, repository-aware triage summary with open questions or a readiness decision.

Frequently Asked Questions about issue-triage

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

FAQPage Schema
How do I determine if a bug report or feature request is actionable for implementation?

To determine if an issue is actionable for implementation, analyze the report against repository docs, code, and tests to classify it, identify blocking gaps, and define concrete acceptance boundaries.

What is issue triage and how does it work with repository-aware analysis?

Issue triage classifies incoming bugs, enhancements, and mixed reports by inspecting project guidance, code, and tests to validate claims, producing a structured artifact with readiness decisions and open questions.

How do I triage GitHub issues without bouncing back and forth with the reporter?

You can triage issues without reporter interaction by performing repository-aware analysis to identify blocking gaps, validate claims against code, and produce a Markdown triage summary with unresolved questions.

Can I use issue triage for both bug reports and enhancement review?

Yes, issue triage applies to bug reports, feature requests, and mixed issue descriptions, classifying each item and determining whether it requires more information or is ready for implementation handoff.

What is the best way to generate a triage summary for downstream posting?

The best way to generate a triage summary for downstream posting is to classify the issue, validate it against repository artifacts, and output a single Markdown artifact with classification, evidence, and acceptance boundaries.