triage

Manage GitHub issues and pull requests through a structured triage state machine.

Updated Dec 17, 2025

Search Tags:#automation #workflow #github #triage #issue-tracking #agent-brief

Ready to run

npx skills add https://github.com/Frantss/oxform --skill triage-frantss

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the management of GitHub issues and pull requests by enforcing a consistent state machine, ensuring that every item is categorized, verified, and documented with high-quality agent briefs.

Core Features & Use Cases

State Machine Management: Automatically moves issues through defined roles like needs-triage, ready-for-agent, and wontfix.
Agent Brief Generation: Standardizes the creation of authoritative specifications for AFK agents to execute.
Knowledge Base Integration: Automatically checks against an out-of-scope database to prevent re-litigating previously rejected feature requests.

Quick Start

Invoke the triage skill by asking it to show you all issues that currently need your attention.

Frequently Asked Questions about triage

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

FAQPage Schema

How do I automate GitHub issue triage workflows?▼

Automating GitHub issue triage involves moving items through a structured state machine of roles like needs-triage to ready-for-agent. This skill enforces consistent documentation standards and generates standardized agent-ready briefs for execution.

What is an agent brief in GitHub issue tracking?▼

An agent brief in GitHub issue tracking is an authoritative specification generated for AFK agents to execute. It standardizes task documentation during the transition from initial reporting to an actionable state.

How do I prevent duplicate rejected feature requests in GitHub?▼

Preventing duplicate rejected feature requests in GitHub requires checking new issues against an out-of-scope knowledge base. This deduplication process stops the re-litigating of previously rejected concepts.

Can I use a state machine to manage pull request lifecycle transitions?▼

Using a state machine to manage pull request lifecycle transitions enforces consistent categorization across defined roles like wontfix or ready-for-agent. This ensures every item is verified and documented.

Does this issue tracking automation require external dependencies?▼

This issue tracking automation does not require external dependencies to function. It operates independently to manage GitHub issue states and generate standardized agent briefs.