triage

Organize GitHub issues and pull requests into triage states with categories.

1|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/ian-pascoe/dotfiles-chezmoi --skill triage-ian-pascoe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/ian-pascoe/dotfiles-chezmoi/tree/main/dot_agents/skills/triage
Command: npx skills add https://github.com/ian-pascoe/dotfiles-chezmoi --skill triage-ian-pascoe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns a noisy issue tracker into a clear workflow by classifying reports, checking whether requests are already implemented, and deciding what needs more information, an agent brief, or a human decision.

Core Features & Use Cases

  • Issue and PR triage: Sorts incoming work into bug, enhancement, needs-triage, needs-info, ready-for-agent, ready-for-human, or wontfix states.
  • Context gathering and verification: Reviews the issue or PR, checks the diff when relevant, and compares the request against existing code and prior out-of-scope decisions.
  • Agent-ready writing: Produces durable briefs and triage notes that capture current findings, acceptance criteria, and boundaries for follow-up work.
  • Use case: A maintainer asks what needs attention or points to a specific issue, and the Skill recommends the next state with a reasoned summary of the tracker and codebase.

Quick Start

Ask the triage skill to review a specific GitHub issue or pull request and recommend the next state with a concise summary.

Frequently Asked Questions about triage

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

FAQPage Schema
How do I triage GitHub issues and pull requests into actionable workflow states?

Triage GitHub issues and pull requests by sorting them into a state machine with categories like needs-info, ready-for-agent, ready-for-human, or wontfix. This classifies reports and decides what needs more information, an agent brief, or a human decision.

What is the best way to check if a GitHub issue request is already implemented?

Checking if a GitHub issue request is already implemented involves reviewing the issue, checking the diff when relevant, and comparing the request against existing codebase features and prior out-of-scope decisions to verify current implementation status.

How do I generate agent-ready briefs from GitHub pull requests for maintainers?

Generate agent-ready briefs from GitHub pull requests by producing durable triage notes that capture current findings, acceptance criteria, and boundaries for follow-up work, turning noisy tracker reports into clear action items.

Can I use automated triage for maintainer workflows with bugs and enhancement requests?

Automated triage applies directly to maintainer workflows needing discovery, context gathering, and verification for bugs and enhancements. It handles exact rules for already implemented work, rejected requests, and needs-info follow-up tracking.

What are the limitations of using a triage state machine for issue discovery?

Limitations of a triage state machine include requiring durable recommendations and exact handling rules for edge cases. It focuses strictly on classifying and briefing GitHub issues rather than automatically resolving or merging the reported code changes.