triage

Classify and manage software issue tracker workflows with evidence-based state transitions.

Updated May 3, 2026

Search Tags:#workflow #github #maintenance #issue tracking #triage #bug reporting

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the cognitive load and inconsistency associated with managing high-volume issue trackers by providing a structured, evidence-based framework for classifying and responding to incoming work.

Core Features & Use Cases

Neutral Workflow Management: Standardizes issue states like needs-triage, needs-info, and planned to ensure consistent project health.
Redundancy Detection: Automatically searches existing issues, closed work, and documentation to prevent duplicate requests or re-litigating rejected concepts.
External PR Assessment: Provides a safe, non-mutating analysis of external contributions to help maintainers make informed decisions.

Quick Start

Invoke the triage skill to review the current status of issue number 42 and provide a recommendation.

Frequently Asked Questions about triage

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

FAQPage Schema

How do I automate issue triage for a high-volume GitHub repository?▼

Automate issue triage by applying evidence-based state transitions to classify bug reports and feature requests into states like needs-triage, needs-info, and planned. This standardizes workflow management and reduces the cognitive load of maintaining project health.

What is the best way to detect duplicate bug reports in an issue tracker?▼

Detect duplicate bug reports through redundancy analysis that searches existing issues, closed work, and documentation. This prevents re-litigating rejected concepts and avoids duplicate requests by maintaining institutional memory.

How does evidence-based issue state transition work for software maintenance?▼

Evidence-based issue state transition works by classifying bug reports and feature requests through contextual analysis of local markdown files or project-specific trackers. It determines appropriate triage states and updates them based on documented evidence.

Can I use markdown files for issue tracking instead of a dedicated platform?▼

You can use local markdown-based issue files for issue tracking. The triage process performs contextual analysis and state updates directly on these files, requiring no external dependencies to manage workflow states.

Does triage support non-mutating analysis for external pull requests?▼

Triage supports non-mutating analysis for external pull requests. It provides a safe assessment of external contributions to help maintainers make informed decisions without automatically modifying the repository state.

When should I document out-of-scope issues during the triage workflow?▼

Document out-of-scope issues during triage to maintain institutional memory and prevent future duplicate requests. Recording rejected concepts ensures the workflow captures evidence-based decisions and avoids re-litigating closed work.