triage

Name: triage
Availability: InStock
Author: cchrisv

Move GitHub issues through classification and state transition workflows.

Updated Apr 27, 2026

Search Tags:#workflow #github #issues #triage #feature requests #agent briefs #bug review

Ready to run

npx skills add https://github.com/cchrisv/newtonSelector --skill triage-cchrisv

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/cchrisv/newtonSelector/tree/main/.agents/skills/triage
Command: npx skills add https://github.com/cchrisv/newtonSelector --skill triage-cchrisv

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill reduces the complexity of managing incoming project issues by providing a structured workflow for classification, evaluation, and routing decisions.

Core Features & Use Cases

Issue Workflow Management: Guides issues through category and state roles such as bugs, enhancements, needs-triage, and ready-for-agent.
Agent Preparation: Creates durable specifications for coding agents and captures acceptance criteria, scope boundaries, and implementation context.
Use Case: Help maintainers review incoming GitHub issues, identify the right workflow state, prepare agent-ready tasks, or preserve decisions about rejected feature requests.

Quick Start

Use the triage skill to review open issues, recommend their categories and states, and prepare any selected issue for the appropriate workflow stage.

Frequently Asked Questions about triage

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

FAQPage Schema

How do I manage GitHub issue triage workflows for incoming bugs and feature requests?▼

Maintainers handle GitHub issue triage by guiding issues through defined classification and state transitions, covering bug evaluation, enhancement review, and agent preparation for downstream coding tasks.

What is the best way to prepare GitHub issues as agent-ready tasks for coding agents?▼

To prepare GitHub issues for coding agents, create durable agent briefs that capture acceptance criteria, scope boundaries, and implementation context, ensuring controlled workflow execution.

How do I track rejected feature requests and out-of-scope GitHub issues?▼

Track rejected feature requests by maintaining out-of-scope records that preserve maintainer decisions, ensuring rejected features are documented within the GitHub issue triage workflow.

Can I use this triage workflow for both bug review and enhancement evaluation on GitHub?▼

Yes, the triage workflow supports GitHub bug review and enhancement evaluation by applying contextual analysis, reproducible bug checks, and structured role mapping to classify and route issues.

Does issue triage require structured role mapping for workflow state transitions?▼

Yes, issue triage requires structured role mapping to move GitHub issues through classification states such as needs-triage, bugs, enhancements, and ready-for-agent for controlled workflow execution.

What limitations exist when moving GitHub issues through classification states in a triage workflow?▼

Limitations include the requirement for reproducible bug checks and contextual analysis; GitHub issues lacking sufficient implementation context cannot be reliably transitioned to ready-for-agent states.