feat: add issue-triage agentic workflow (gh-aw IssueOps) - #185
Merged
Elizabeth Maher (EMaher) merged 12 commits intoJun 24, 2026
Merged
Conversation
Implements gh-aw IssueOps pattern for automated issue triage on open. Key design decisions: - Issue content passed as user context; routing/team policy as system context - Contract tests enforce context separation (prevents prompt injection) - Post-check validates triage comments include confidence + uncertainty - Safe outputs constrain labels to advisory-only allowed list (max 3) - Governance labels (squad:*, go:*, priority:*) explicitly blocked - Single triage recommendation comment per issue for human review Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Assignee routing will be determined after the go/no-go decision. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
The triage agent can now call Squad Agent team members for domain-specific analysis when issues cross specializations. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
Author
|
Workflow follows Issue Triage Assistant Agentic Workflow example. |
Elizabeth Maher (EMaher)
requested review from
Alexander Zaslonov (azaslonov) and
Copilot
June 23, 2026 17:07
Contributor
There was a problem hiding this comment.
Pull request overview
This PR introduces a new gh-aw IssueOps workflow to automatically triage newly opened GitHub issues by generating an advisory comment and applying a constrained set of advisory labels, using squad routing/team policy as “system context” and issue text as “user context”.
Changes:
- Adds a new
.github/workflows/issue-triage.mdagentic workflow triggered onissues: opened. - Implements context preparation + a “context separation” contract test before the agent runs.
- Adds a post-step schema check to enforce that the agent’s triage comment includes both confidence and uncertainty fields.
Contributor
Author
|
Copilot Have squad handle the comments. |
Alexander Zaslonov (azaslonov)
approved these changes
Jun 23, 2026
Contributor
Author
|
Related to #90 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
New issues currently require manual triage -- reading content, deciding on type/effort labels, and routing to the right domain. This PR adds an automated first-pass triage using the gh-aw IssueOps pattern so every opened issue gets an immediate recommendation comment and advisory labels, reducing time-to-triage for human reviewers.
Approach
Adds
.github/workflows/issue-triage.md, a gh-aw agentic workflow that triggers onissues: [opened]. The design enforces strict security boundaries between untrusted issue content and trusted repo policy:steps:write issue title/body into ausercontext file and.squad/routing.md+.squad/team.mdinto asystemcontext file. A contract-test step verifies no cross-contamination before the agent runs.type:bug,type:feature,type:question,type:documentation,duplicate,effort:*) with governance labels (squad:*,go:*,priority:*,override:*) blocked. Max 3 labels, max 1 comment.post-steps:handler validates the agent's triage comment includes both a confidence score and an uncertainty indicator, failing the workflow if either is missing..github/workflows/sync-squad-labels.ymlso the advisory triage labels exist in the repository and preserves the existingtype:featuredefinition.The triage comment is advisory only -- a human reviews it and applies governance labels afterward.
Non-obvious decisions
post-steps:is intentionally broad to avoid false negatives while still catching missing fields entirely.Suggested assigneewas intentionally omitted from the comment format; assignee routing will be added after the go/no-go decision process is defined.