Oss Maintainer Triage

OSS Maintainer Triage

Use this skill to help maintainers turn open-source project activity into clear, reviewable work.

Workflow

1. Gather the artifact under triage:
   • issue, PR, discussion, changelog, commit list, failing CI log, reproduction, or maintainer notes.
2. Classify the work:
   • bug, feature, regression, docs, test, security, dependency, release, question, duplicate, needs reproduction, or wontfix.
3. Identify maintainer action:
   • ask for information
   • reproduce locally
   • request tests
   • request design decision
   • review code
   • merge
   • close with reason
4. Preserve uncertainty:
   • Do not claim a bug is confirmed unless evidence shows it.
   • Distinguish user reports from verified behavior.
   • Avoid assigning severity without impact evidence.
5. Produce short, paste-ready maintainer output.

Suggested Labels

Prefer common labels unless the repository has its own taxonomy:

• bug
• enhancement
• documentation
• question
• needs-reproduction
• needs-tests
• security
• dependencies
• release
• good-first-issue

Output Format

Summary
- One sentence.

Suggested Labels
- label names

Maintainer Decision
- next action and why

Reply Draft
Short maintainer-facing response.

For PRs, include:

• behavioral risk
• missing tests
• files likely needing review
• merge/block recommendation