From 0da2942d3d55c5c64e15b557c96b8d7ded553f16 Mon Sep 17 00:00:00 2001 From: Gunju Kim Date: Thu, 19 Feb 2026 00:10:32 +0000 Subject: [PATCH] self-development: Add priority classification to triage agent Extend the triage agent prompt to also assess and apply priority/* labels alongside the existing kind/* classification. This reduces maintainer toil by automating the priority assessment step. Currently 29 open issues carry the needs-priority label, requiring manual classification. The triage agent already reads the issue content deeply enough to make a reasonable priority judgment. Priority guidelines match the existing label usage patterns: - critical-urgent: production broken, security, blocking issues - imporant-soon: significant bugs or needed features - import-longterm: valuable but not time-sensitive improvements - backlog: nice-to-have, cosmetic, or speculative ideas Co-Authored-By: Claude Opus 4.6 --- self-development/axon-triage.yaml | 20 +++++++++++++++++++- 1 file changed, 19 insertions(+), 1 deletion(-) diff --git a/self-development/axon-triage.yaml b/self-development/axon-triage.yaml index de74ec5..6331531 100644 --- a/self-development/axon-triage.yaml +++ b/self-development/axon-triage.yaml @@ -27,7 +27,7 @@ spec: promptTemplate: | You are a triage agent for the Axon project (github.com/axon-core/axon). Your job is to determine whether the following issue is still valid, classify - it with a kind/* label, and post a single triage comment using `gh`. + it with kind/* and priority/* labels, and post a single triage comment using `gh`. --- Issue #{{.Number}}: {{.Title}} @@ -50,6 +50,22 @@ spec: Apply the label: `gh issue edit {{.Number}} --add-label --remove-label needs-kind` + ### 1b. Assess priority + Based on the issue content and its impact, apply exactly one `priority/*` label: + - `priority/critical-urgent` — production broken, data loss, security vulnerability, or blocking all development + - `priority/imporant-soon` — significant bug or feature needed for upcoming work; should be addressed soon + - `priority/import-longterm` — valuable improvement but not time-sensitive; can be planned for a future milestone + - `priority/backlog` — nice-to-have, minor cosmetic issues, or speculative ideas + + Guidelines: + - Bugs that affect correctness → at least `imporant-soon` + - Documentation-only issues → usually `import-longterm` or `backlog` + - Feature requests for existing gaps → usually `imporant-soon` or `import-longterm` + - Broad proposals or speculative ideas → usually `backlog` + + Apply the label: + `gh issue edit {{.Number}} --add-label --remove-label needs-priority` + ### 2. Check if already fixed Check whether this issue has already been resolved: - Search for merged PRs that reference this issue: @@ -85,6 +101,8 @@ spec: **Kind**: + **Priority**: + **Status**: STILL VALID / ALREADY FIXED / OUTDATED / DUPLICATE **Evidence**: