Support primary agent issue classification and agent:priority-high triage by vkodithala · Pull Request #500 · warpdotdev/oz-for-oss

vkodithala · 2026-09-08T14:19:53Z

Description

Updates the automated issue triage workflow in oz-for-oss to support classifying open-source issues into primary categories with provenance (agent:bug, agent:feature, agent:security, agent:documentation) and tagging urgent issues (regressions, crashes/panics/data loss, security reports) with agent:priority-high.

What changed

core/workflows/triage_new_issues.py:
- Defined PRIMARY_ISSUE_TYPES = ("agent:bug", "agent:feature", "agent:security", "agent:documentation") and parametrized primary issue types in build_triage_prompt.
- Added PRIMARY_ISSUE_TYPES to PRIMARY_TRIAGE_LABELS and defined PRIORITY_LABELS = {"agent:priority-high", "priority:high"}.
- Updated apply_triage_result to replace prior primary triage labels on retriage via should_replace_triage_label and preserve agent:priority-high in managed_labels.
.github/issue-triage/config.json:
- Added label specs for agent:bug (#8ff8fd), agent:feature (#f47f64), agent:security (#a0ce9f), agent:documentation (#5f966f), and agent:priority-high (#b60205).
.agents/skills/triage-issue/SKILL.md:
- Updated Step 2 to mandate primary type classification, and Steps 4 and 7 to emphasize tagging regressions, crashes, and security reports with agent:priority-high.
tests/test_triage.py:
- Added unit tests covering application and retriage replacement of agent:feature, agent:security, and agent:priority-high.

Manual Operational Steps Required for Rollout

Backfill past open issues: Run an agent sweep over existing open issues in warpdotdev/warp to classify them into agent:bug, agent:feature, agent:security, or agent:documentation, and tag high-priority regressions/crashes with agent:priority-high.
Add relevant labels to warp repo: Ensure the agent:bug (#8ff8fd), agent:feature (#f47f64), agent:security (#a0ce9f), agent:documentation (#5f966f), and agent:priority-high (#b60205) labels exist in warpdotdev/warp (addressed via Update triage taxonomy with agent: primary types and agent:priority-high warp#15868).

Stack & Connections

This PR is part of a 3-repo stack to pause non-KTLO triage noise ahead of Factory GA:

warpdotdev/warp (PR Update triage taxonomy with agent: primary types and agent:priority-high warp#15868): Configures repository-level label taxonomy and local companion skills.
warpdotdev/oz-for-oss (this PR): Directs automated triage to output primary type classifications and agent:priority-high.
warpdotdev/ossie (PR https://github.com/warpdotdev/ossie/pull/64): Updates Slack triage alerts to suppress individual messages/pings for non-prioritized issues, reserving individual Slack alerts for agent:security and agent:priority-high issues.

Co-Authored-By: Warp agent@warp.dev

Update automated issue triage to support feature and security classifications alongside priority:high tagging for regressions, panics, crashes, and security vulnerabilities. Co-Authored-By: Warp <agent@warp.dev>

warp-for-oss · 2026-09-08T14:20:06Z

@vkodithala

I'm starting a first review of this pull request.

You can view the conversation on Warp.

I completed the review and no human review was requested for this pull request.

Comment /warp-agent-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz

warp-for-oss

Overview

This PR updates the issue triage workflow and triage skill guidance to classify issues into primary labels and apply priority:high for urgent regressions, crashes, data loss, and security reports. It also extends retriage label handling and adds unit coverage for feature, security, and priority:high labels.

Concerns

No blocking correctness, security, comment-quality, test-quality, or spec-alignment concerns were found in the annotated diff.
No approved or repository spec context was supplied, so there was no material spec drift to flag.

Verdict

Found: 0 critical, 0 important, 0 suggestions

Approve

Comment /warp-agent-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz

vkodithala

Mostly LG, two small changes we should consider.

vkodithala · 2026-09-08T15:42:13Z

   - the user's hypotheses, proposed fixes, or root-cause claims
   - the missing details that block confident triage
-2. Classify whether the issue is primarily a bug report, enhancement request, documentation issue, or needs more information. As part of classification, detect reports that cannot be resolved through OSS contributions — billing inquiries, plan changes, refund requests, subscription or account management, pricing questions, and payment issues. These belong with the Warp support team, not OSS contributors: request the `warp:needs-support` label, set `close_issue` to `true`, and put a brief reporter-facing message in `statements` directing the user to contact Warp support (for example, "For plan changes or refund requests, please contact Warp support at support@warp.dev"). For these reports, do not produce follow-up questions, root-cause analysis, or duplicate detection — the support escalation is the triage outcome. Do not set `close_issue` for issues that can be addressed via OSS contributions; leave it `false` or omitted.
+2. Classify every issue into at least one primary type (`bug`, `feature`, `security`, `documentation`). As part of classification, detect reports that cannot be resolved through OSS contributions — billing inquiries, plan changes, refund requests, subscription or account management, pricing questions, and payment issues. These belong with the Warp support team, not OSS contributors: request the `warp:needs-support` label, set `close_issue` to `true`, and put a brief reporter-facing message in `statements` directing the user to contact Warp support (for example, "For plan changes or refund requests, please contact Warp support at support@warp.dev"). For these reports, do not produce follow-up questions, root-cause analysis, or duplicate detection — the support escalation is the triage outcome. Do not set `close_issue` for issues that can be addressed via OSS contributions; leave it `false` or omitted.


Yeah again, related to my feedback on the downstream PR here; I think the right thing to do is add provenance directly to these labels.

vkodithala · 2026-09-08T15:43:13Z

            triage. Be direct and precise; do not re-emit the triage
            shape's fields when you choose this mode.
        - Prefer labels from the `triage_config` object in `{_REPOSITORY_TRIAGE_CONTEXT_ATTACHMENT}`.
+        - Classify every issue into at least one primary type (`bug`, `feature`, `security`, `documentation`). Tag regressions ("broke in recent version", "worked before"), crashes/panics/data loss, or security vulnerabilities with `priority:high`.


nit: Is there a way to parametrize primary labels? Don't we keep this as a var somewhere?

Update automated triage to emit agent:bug, agent:feature, agent:security, and agent:documentation, and parametrize primary issue types in the prompt builder. Co-Authored-By: Warp <agent@warp.dev>

Update prompt, config, skill, and test cases to use agent:priority-high. Co-Authored-By: Warp <agent@warp.dev>

…igh (#15868) ## Description Updates the repository's issue triage configuration and companion triage skill to encode provenance directly into agent-assigned classifications (`agent:bug`, `agent:feature`, `agent:security`, `agent:documentation`) and support urgent issue prioritization with `agent:priority-high`. ### What changed - `.github/issue-triage/config.json`: Added `agent:bug` (`#8ff8fd`), `agent:feature` (`#f47f64`), `agent:security` (`#a0ce9f`), `agent:documentation` (`#5f966f`), and `agent:priority-high` (`#b60205`) label definitions. - `.agents/skills/triage-issue-local/SKILL.md`: Documented the primary agent types and `agent:priority-high` in the label taxonomy section and updated heuristics to direct the triage agent to classify issues into primary agent types (exempting billing/appeals reports that route to support via `warp:needs-support`) and explicitly bias toward applying `agent:priority-high` to regressions ("broke in recent version", "worked before"), crashes/panics, data loss, and security vulnerabilities. ### Stack & Connections This PR is part of a 3-repo stack to pause non-KTLO triage noise ahead of Factory GA: - **`warpdotdev/warp`** (this PR): Defines the agent label taxonomy and repository-local skill guidance. - **`warpdotdev/oz-for-oss`** (PR warpdotdev/oz-for-oss#500): Updates the automated triage workflow to classify issues into primary agent types, parametrize primary types in prompt construction, and preserve `agent:priority-high` during retriage. - **`warpdotdev/ossie`** (PR warpdotdev/ossie#64): Updates issue triage Slack alerts to suppress individual messages/pings for non-prioritized issues, reserving individual Slack alerts for `agent:security` and `agent:priority-high` issues. Co-Authored-By: Warp <agent@warp.dev> --------- Co-authored-by: Warp <agent@warp.dev>

Support primary issue classification and priority:high triage

d3e78e0

Update automated issue triage to support feature and security classifications alongside priority:high tagging for regressions, panics, crashes, and security vulnerabilities. Co-Authored-By: Warp <agent@warp.dev>

warp-for-oss Bot reviewed Sep 8, 2026

View reviewed changes

vkodithala commented Sep 8, 2026

View reviewed changes

vkodithala requested a review from kevinyang372 September 8, 2026 15:51

kevinyang372 approved these changes Sep 8, 2026

View reviewed changes

Use agent: prefix for triage issue types and parametrize prompt

d38c2c2

Update automated triage to emit agent:bug, agent:feature, agent:security, and agent:documentation, and parametrize primary issue types in the prompt builder. Co-Authored-By: Warp <agent@warp.dev>

vkodithala mentioned this pull request Sep 8, 2026

Update triage taxonomy with agent: primary types and agent:priority-high warpdotdev/warp#15868

Merged

vkodithala changed the title ~~Support primary issue classification and priority:high triage~~ Support primary agent issue classification and priority:high triage Sep 8, 2026

Use agent:priority-high for triage priority label

8b5f6de

Update prompt, config, skill, and test cases to use agent:priority-high. Co-Authored-By: Warp <agent@warp.dev>

vkodithala changed the title ~~Support primary agent issue classification and priority:high triage~~ Support primary agent issue classification and agent:priority-high triage Sep 8, 2026

vkodithala merged commit a2bb45f into main Sep 9, 2026
4 checks passed

Navigation Menu

Repository navigation

Support primary agent issue classification and agent:priority-high triage - #500

Support primary agent issue classification and agent:priority-high triage#500
vkodithala merged 3 commits into
mainfrom
varoon/feature-priority-triage

vkodithala commented Sep 8, 2026 •

edited

Loading

Uh oh!

warp-for-oss Bot commented Sep 8, 2026 •

edited

Loading

Uh oh!

warp-for-oss Bot left a comment

Uh oh!

vkodithala left a comment

Uh oh!

vkodithala Sep 8, 2026

Uh oh!

vkodithala Sep 8, 2026

Uh oh!

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Conversation

vkodithala commented Sep 8, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Description

What changed

Manual Operational Steps Required for Rollout

Stack & Connections

Uh oh!

warp-for-oss Bot commented Sep 8, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

warp-for-oss Bot left a comment

Choose a reason for hiding this comment

Overview

Concerns

Verdict

Uh oh!

vkodithala left a comment

Choose a reason for hiding this comment

Uh oh!

vkodithala Sep 8, 2026

Choose a reason for hiding this comment

Uh oh!

vkodithala Sep 8, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

vkodithala commented Sep 8, 2026 •

edited

Loading

warp-for-oss Bot commented Sep 8, 2026 •

edited

Loading