Add triage-issues-local skill for OS issue triage#170
Conversation
Add a new skill for the Oz management agent to triage community issues on the docs repo. The skill classifies issues, identifies affected pages, assesses priority, checks for duplicates, applies labels (triage + priority), and posts a structured comment with a welcome preamble and reviewer instructions. Labels (priority/high, priority/medium, priority/low, triage, and improve or update documentation) were created directly on the repo. Co-Authored-By: Oz <oz-agent@warp.dev>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
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 Powered by Oz |
![oz-for-oss[bot]](https://avatars.githubusercontent.com/in/3450139?s=60&v=4){kind=small}
There was a problem hiding this comment.
Overview
This PR adds a repo-local docs issue triage skill. The main concerns are that the skill is not located/named where the triage workflow resolves repo-local companion skills, and its instructions redefine the core workflow by asking the agent to mutate GitHub directly instead of returning triage_result.json for the workflow to apply.
Concerns
- The added skill uses
.agents/skills/triage-issues-local/SKILL.md/triage-issues-local, but the dispatch resolver looks for.agents/skills/triage-issue-local/SKILL.md, so this guidance will not be loaded. - The skill asks the agent to apply labels and post comments directly, which conflicts with the core triage workflow's JSON-artifact contract and can produce duplicate or unauthorized GitHub mutations.
- The duplicate search instruction uses an unpaginated
gh issue listcall instead of the shared repository-wide dedupe workflow, so it can miss older duplicate issues.
Verdict
Found: 0 critical, 4 important, 0 suggestions
Request changes
Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).
Powered by Oz
| @@ -0,0 +1,124 @@ | |||
| --- | |||
| name: triage-issues-local | |||
There was a problem hiding this comment.
.agents/skills/triage-issue-local/SKILL.md and name: triage-issue-local when dispatching the core triage-issue workflow, so this pluralized companion will be ignored. Rename the directory/frontmatter to triage-issue-local and mark it as specializing triage-issue.
| ### 6. Check for duplicates | ||
|
|
||
| Search open issues for potential duplicates: | ||
| - Use `gh issue list --repo warpdotdev/docs --state open` to list open issues |
There was a problem hiding this comment.
gh issue list call only returns the first page, so duplicate detection will silently miss older issues. Delegate to the shared dedupe-issue workflow or require a paginated search.
| - **`triage`** — Always apply this. It signals the issue needs human review. | ||
| - **One priority label** — `priority/high`, `priority/medium`, or `priority/low` based on your assessment. | ||
|
|
||
| Use the GitHub CLI or API to apply labels. |
There was a problem hiding this comment.
triage_result.json and then applies labels itself. Calling GitHub directly from the companion violates the core triage-issue output contract and can create duplicate or unauthorized label mutations.
|
|
||
| ### 8. Post the triage comment | ||
|
|
||
| Post a single comment on the issue with three sections: |
There was a problem hiding this comment.
triage_result.json; instructing the agent to post another comment directly can duplicate comments and bypass the maintainer-visible triage format. Describe the desired issue_body content instead.
…nation - Rename triage-issues-local -> triage-issue-local (singular) to match the management agent's resolver convention - Switch from direct label/comment application to triage_result.json artifact output, consistent with the review-pr workflow pattern - Fix unpaginated gh issue list by adding --limit 100 - Add JSON validation step - Update example to show JSON schema instead of raw markdown comment Co-Authored-By: Oz <oz-agent@warp.dev>
Review request — questions for @captainsafiaThis PR adds a
|
| @@ -0,0 +1,117 @@ | |||
| --- | |||
| name: triage-issue-local | |||
There was a problem hiding this comment.
You can actually skip most of the content that tells the agent to read the issue and write out the triage_result.json. The OSS workflows will handle that. You can keep this one focused strictly on the rules.
The version in the warp repo is a good example of what the target structure would look like.
2 participants
Summary
Add automated issue triage for the newly open-sourced docs repo. This PR adds a
triage-issues-localskill that the Oz OSS repo management agent uses to triage community issues, plus creates the supporting label taxonomy on the repo.Changes
New:
.agents/skills/triage-issues-local/SKILL.mdtriage+ priority labels automaticallyLabels created on the repo (already live)
priority/high(red) — Factually incorrect info, broken page, security-relatedpriority/medium(yellow) — Outdated content, confusing instructions, incomplete coveragepriority/low(green) — Typos, minor formatting, nice-to-have improvementstriage(gray) — Applied automatically; removed once a human reviewsimprove or update documentation(blue) — Fixes the missing label referenced by the CONTENT.yml issue templateContext
Co-Authored-By: Oz oz-agent@warp.dev