Skip to content

self-development: Add priority classification to triage agent #385

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
axon-agent wants to merge 1 commit into from
Closed

self-development: Add priority classification to triage agent #385

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 19 additions & 1 deletion self-development/axon-triage.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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}}
Expand All @@ -50,6 +50,22 @@ spec:
Apply the label:
`gh issue edit {{.Number}} --add-label <kind-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
Copy link

@cubic-dev-ai cubic-dev-ai bot Feb 19, 2026 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1: Typo in label name: priority/imporant-soon → priority/important-soon. The agent will apply a misspelled label via gh issue edit, creating a bogus label instead of matching the existing one. The same typo also appears in the guidelines below (imporant-soon).

Prompt for AI agents 
Check if this issue is valid — if so, understand the root cause and fix it. At self-development/axon-triage.yaml, line 56:

<comment>Typo in label name: `priority/imporant-soon` → `priority/important-soon`. The agent will apply a misspelled label via `gh issue edit`, creating a bogus label instead of matching the existing one. The same typo also appears in the guidelines below (`imporant-soon`).</comment>

<file context>
@@ -50,6 +50,22 @@ spec:
+      ### 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
</file context>
Suggested change
- `priority/imporant-soon` — significant bug or feature needed for upcoming work; should be addressed soon
- `priority/important-soon` — significant bug or feature needed for upcoming work; should be addressed soon
Fix with Cubic

- `priority/import-longterm` — valuable improvement but not time-sensitive; can be planned for a future milestone
Copy link

@cubic-dev-ai cubic-dev-ai bot Feb 19, 2026 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1: Typo in label name: priority/import-longterm → priority/important-longterm. The agent will apply a misspelled label via gh issue edit, creating a bogus label instead of matching the existing one. The same typo also appears in the guidelines below (import-longterm).

Prompt for AI agents 
Check if this issue is valid — if so, understand the root cause and fix it. At self-development/axon-triage.yaml, line 57:

<comment>Typo in label name: `priority/import-longterm` → `priority/important-longterm`. The agent will apply a misspelled label via `gh issue edit`, creating a bogus label instead of matching the existing one. The same typo also appears in the guidelines below (`import-longterm`).</comment>

<file context>
@@ -50,6 +50,22 @@ spec:
+      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
+
</file context>
Suggested change
- `priority/import-longterm` — valuable improvement but not time-sensitive; can be planned for a future milestone
- `priority/important-longterm` — valuable improvement but not time-sensitive; can be planned for a future milestone
Fix with Cubic

- `priority/backlog` — nice-to-have, minor cosmetic issues, or speculative ideas

Guidelines:
- Bugs that affect correctness → at least `imporant-soon`
Copy link

@cubic-dev-ai cubic-dev-ai bot Feb 19, 2026 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1: Typo: imporant-soon → important-soon.

Prompt for AI agents 
Check if this issue is valid — if so, understand the root cause and fix it. At self-development/axon-triage.yaml, line 61:

<comment>Typo: `imporant-soon` → `important-soon`.</comment>

<file context>
@@ -50,6 +50,22 @@ spec:
+        - `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`
</file context>
Suggested change
- Bugs that affect correctness → at least `imporant-soon`
- Bugs that affect correctness → at least `important-soon`
Fix with Cubic

- Documentation-only issues → usually `import-longterm` or `backlog`
Copy link

@cubic-dev-ai cubic-dev-ai bot Feb 19, 2026 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1: Typo: import-longterm → important-longterm.

Prompt for AI agents 
Check if this issue is valid — if so, understand the root cause and fix it. At self-development/axon-triage.yaml, line 62:

<comment>Typo: `import-longterm` → `important-longterm`.</comment>

<file context>
@@ -50,6 +50,22 @@ spec:
+
+      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`
</file context>
Suggested change
- Documentation-only issues → usually `import-longterm` or `backlog`
- Documentation-only issues → usually `important-longterm` or `backlog`
Fix with Cubic

- Feature requests for existing gaps → usually `imporant-soon` or `import-longterm`
Copy link

@cubic-dev-ai cubic-dev-ai bot Feb 19, 2026 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1: Same typos propagated into the guidelines: imporant-soon → important-soon and import-longterm → important-longterm.

Prompt for AI agents 
Check if this issue is valid — if so, understand the root cause and fix it. At self-development/axon-triage.yaml, line 63:

<comment>Same typos propagated into the guidelines: `imporant-soon` → `important-soon` and `import-longterm` → `important-longterm`.</comment>

<file context>
@@ -50,6 +50,22 @@ spec:
+      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`
+
</file context>
Suggested change
- Feature requests for existing gaps → usually `imporant-soon` or `import-longterm`
- Feature requests for existing gaps → usually `important-soon` or `important-longterm`
Fix with Cubic

- Broad proposals or speculative ideas → usually `backlog`

Apply the label:
`gh issue edit {{.Number}} --add-label <priority-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:
Expand Down Expand Up @@ -85,6 +101,8 @@ spec:

**Kind**: <kind label applied>

**Priority**: <priority label applied>

**Status**: STILL VALID / ALREADY FIXED / OUTDATED / DUPLICATE

**Evidence**:
Expand Down
Loading