triage

Files (6)

• AGENT-BRIEF.md
• OUT-OF-SCOPE.md
• SKILL.md
• openai.yaml · agents/
• item-review.md
• roles.md

SKILL.md (first lines)

# Triage

Resolve the requested issue or PR using existing tracker configuration. A queue/status request is read-only. Explicitly requested label, comment, or closure operations may proceed within their stated scope; generic analysis does not authorize tracker mutations.

- **Queue review:** query unlabeled items, `needs-triage`, and `needs-info` items with new reporter activity. Use the configured external-PR filter for discovery; an explicitly named PR is still in scope. Return counts and concise summaries.
- **Item review:** read [item-review.md](item-review.md) for evidence gathering, reproduction, prior decisions, and outcome preparation. Consult [roles.md](roles.md) for the state model and configured label mapping.
- **Explicit state change:** apply the requested transition when the target and role are clear. Ask only about conflicting state or a material unresolved choice; do not re-grill an already resolved decision.

For an agent-ready brief, read [AGENT-BRIEF.md](AGENT-BRIEF.md). For a rejected enhancement, read [OUT-OF-SCOPE.md](OUT-OF-SCOPE.md). Do not create rejection records for behavior that already exists.

Before an authorized post, apply the repository's disclosure convention; this workflow's default prefix is `> *This was generated by AI during triage.*`. Reuse prior triage notes, distinguish verified behavior from uncertainty, and avoid repeating answered questions. Finish with the requested analysis or authorized changes and their evidence.

From jamesdebatty/skills, MIT.

More from jamesdebatty/skills