github-issue-triage

Classifies GitHub issues and recommends next workflow states for maintainers.

1|1|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/robertolopezlopez/agent-skills --skill github-issue-triage-robertolopezlopez
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-issue-triage
Source: https://github.com/robertolopezlopez/agent-skills/tree/main/skills/core/github-issue-triage
Command: npx skills add https://github.com/robertolopezlopez/agent-skills --skill github-issue-triage-robertolopezlopez

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps maintainers turn incomplete or ambiguous GitHub issues into structured triage decisions by classifying reports, identifying missing information, and recommending next workflow states.

Core Features & Use Cases

  • Issue Classification: Analyze GitHub issue context to recommend categories such as bug or enhancement and assess readiness for follow-up work.
  • Triage Workflow Guidance: Produce maintainer-focused summaries, missing information checks, and next-step recommendations while keeping issue handling separate from implementation.
  • Use Case: A maintainer receives a new GitHub issue with unclear impact and uses this Skill to determine whether it needs more information, technical investigation, or can move toward implementation.

Quick Start

Use the github-issue-triage skill to review the provided GitHub issue context and prepare a maintainer triage recommendation.

Frequently Asked Questions about github-issue-triage

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

FAQPage Schema
How do I triage GitHub issues with incomplete information?

To triage GitHub issues with incomplete information, this Skill analyzes available issue context to classify reports and identify missing data needed for follow-up work. It evaluates bug reports and feature requests to recommend actionable next workflow states.

What is the best way to classify GitHub bug reports and feature requests?

The best way to classify GitHub bug reports and feature requests is using issue triage analysis to assess readiness and recommend categories. This Skill evaluates issue summaries to separate ambiguous reports into structured maintainer decisions.

Do I need normalized GitHub issue data from GITHUB-ACCESS.md to use this?

Yes, you need normalized GitHub issue data from GITHUB-ACCESS.md and gh-based transport workflows to use this Skill. It requires this structured context as input to produce evidence-based triage recommendations for maintainer workflows.

How do I determine next workflow states for ambiguous GitHub issues?

You determine next workflow states for ambiguous GitHub issues by applying triage analysis to assess whether reports need more information or technical investigation. The Skill provides maintainer-focused summaries and next-step recommendations while keeping issue handling separate from implementation.

Can this Skill help with maintainer workflow planning after issue classification?

Yes, this Skill helps with maintainer workflow planning after issue classification by producing missing information checks and actionable next-step recommendations. It guides maintainers on whether to request more details, investigate technically, or move toward implementation.