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
…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.
Rewrite triage-issue-local to match the pattern in the warp repo. The core triage-issue skill (managed by the OSS system) handles reading issues, writing triage_result.json, applying labels, posting comments, and checking duplicates. This local skill only provides repo-specific rules: - Heuristics for docs issues (site bugs vs content, URL mapping, source code verification) - Label taxonomy (priority labels, triage, ready-to-implement) - Follow-up question limit (2 max) - Information to check before asking follow-ups - Content structure reference Co-Authored-By: Oz <oz-agent@warp.dev>
|
/oz-review |
|
I'm re-reviewing this pull request in response to a review 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 |
There was a problem hiding this comment.
Overview
This PR adds repo-specific triage guidance for docs issues, including label taxonomy, follow-up patterns, and content structure references.
Concerns
- The companion skill currently instructs agents to apply
ready-to-implement, but the coretriage-issueworkflow reserves that label for maintainers and forbids local overrides from changing reserved label rules.
Verdict
Found: 0 critical, 1 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
Co-authored-by: oz-for-oss[bot] <277970191+oz-for-oss[bot]@users.noreply.github.com>
2 participants
Summary
Add automated issue triage for the newly open-sourced docs repo. The docs repo is already onboarded to the Oz OSS repo management agent (thanks Safia). This PR adds a
triage-issue-localcompanion skill with docs-specific rules the coretriage-issueworkflow uses to specialize its behavior for this repo.Changes
New:
.agents/skills/triage-issue-local/SKILL.mdRepo-specific triage rules for the management agent, following the same pattern as the warp repo's version. Includes:
priority/high,priority/medium,priority/low), status labels (triage,ready-to-implement), and template labels (bug,improve or update documentation)Labels 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 reviewsready-to-implement(green) — Issue is triaged and ready for someone to work onimprove or update documentation(blue) — Fixes the missing label referenced by the CONTENT.yml issue templateContext
Co-Authored-By: Oz oz-agent@warp.dev