triage

Categorize and verify GitHub issues and pull requests into triage states.

Updated Aug 26, 2024

Search Tags:#github #pull requests #issues #workflow management #triage #agent briefs

Ready to run

npx skills add https://github.com/FabienDehopre/my-netatmo-24 --skill triage-fabiendehopre

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/FabienDehopre/my-netatmo-24/tree/main/.agents/skills/triage
Command: npx skills add https://github.com/FabienDehopre/my-netatmo-24 --skill triage-fabiendehopre

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps maintainers organize issue and pull request workflows by turning ambiguous requests into clearly categorized, verified, and actionable work items.

Core Features & Use Cases

Issue State Management: Move issues and external pull requests through structured triage states such as needs-triage, needs-info, ready-for-agent, and wontfix.
Agent Brief Creation: Produce durable specifications with behavioral requirements, acceptance criteria, and scope boundaries for coding agents.
Triage Knowledge Management: Check for existing implementations and rejected feature requests using project context to avoid duplicate work and preserve decisions.

Quick Start

Use the triage skill to review issues needing attention and prepare issue #42 for an agent-ready implementation brief.

Frequently Asked Questions about triage

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

FAQPage Schema

How do I organize GitHub issues and pull requests for automated coding agents?▼

Triage GitHub issues and pull requests by categorizing them into structured states like needs-triage, needs-info, and ready-for-agent, then generating durable implementation briefs with acceptance criteria for coding agents.

What is the best way to prepare ambiguous GitHub issues for agent-ready work?▼

Preparing ambiguous GitHub issues for agent-ready work involves verifying the request, checking for existing implementations, and producing structured specifications with behavioral requirements and clear scope boundaries.

How does triage workflow management handle duplicate issues and rejected feature requests?▼

Triage workflow management tracks out-of-scope knowledge and checks project context for existing implementations or previously rejected feature requests to avoid duplicate work and preserve historical decisions.

Can I use structured triage states to manage external pull requests on GitHub?▼

Yes, you can move external pull requests through structured triage states such as needs-triage, needs-info, ready-for-agent, and wontfix to ensure proper verification and state transitions before implementation.

What should be included in an agent brief for GitHub issue implementation?▼

An agent brief for GitHub issue implementation should include durable specifications, behavioral requirements, acceptance criteria, and defined scope boundaries to support reliable project management and agent handoff.

When should I mark a GitHub issue as wontfix during the triage process?▼

Mark a GitHub issue as wontfix during the triage process when the request falls outside project scope, lacks necessary information after verification, or duplicates a previously rejected feature request.