Automate GitHub issue triage with category and state roles.
npx skills add https://github.com/docs-plus/docs.plus --skill triage-docs-plus
Please help me install this Agent Skill. Skill: triage Source: https://github.com/docs-plus/docs.plus/tree/main/.agents/skills/triage Command: npx skills add https://github.com/docs-plus/docs.plus --skill triage-docs-plus
Manually sorting GitHub issues, preparing specifications for autonomous agents, and tracking rejected feature decisions is inconsistent and time-consuming, leading to duplicated work, lost context, and repeated discussions of previously rejected ideas.
Use the triage skill to evaluate the 5 newest unlabeled GitHub issues, assign appropriate triage roles, and surface any that match previously rejected feature requests in the .out-of-scope directory.
High-intent search queries and answers about installing and using this skill.
Automating GitHub issue triage involves applying a defined state machine of category and state roles to sort incoming bug reports and feature requests. This standardizes issue workflow by assigning labels like needs-triage or ready-for-agent, preventing duplicated work and lost context.
Preparing GitHub issues for autonomous agents requires generating durable agent briefs with concrete acceptance criteria. This avoids stale file and line references, ensuring AFK agents receive fully specified issues for implementation without losing context or encountering outdated references.
Tracking rejected feature requests requires maintaining a persistent out-of-scope knowledge base, such as a .out-of-scope directory. This preserves reasoning for wontfix decisions, preventing new contributors from re-litigating past ideas and deduplicating similar incoming issues.
Yes, this issue triage workflow supports out-of-scope tracking by maintaining a persistent knowledge base of rejected feature requests. It matches incoming issues against previously rejected ideas to prevent re-litigating past decisions and deduplicate similar feature requests.
Yes, you can use a state machine to standardize GitHub issue sorting for open source maintainers. It enforces clear category and state roles, such as needs-triage, ready-for-agent, and wontfix, to consistently sort bug reports and feature requests across the repository.
Durable agent briefs are needed for AFK autonomous agents to avoid stale file and line references during implementation. They include concrete acceptance criteria and fully specified issue context, ensuring autonomous agents can work independently without lost context or duplicated effort.
paialexTriage GitHub issues using a label-based state machine across six states.
wtyler2505Coordinate Claude Code agents across isolated worktrees with dependency DAG enforcement.
TrebuchetDynamicsOrchestrate GitHub issue triage with role-based state transitions and agent briefs.
kvithayathilAutomate GitHub issue triage with a label-based state machine.
