Issue Triage Rotation and Labelling Guide for a Small Open-Source Project
Set up a sustainable way to review incoming issues.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Create an issue triage guide for a small GitHub project. The project and community size: [PROJECT_AND_COMMUNITY]. Typical incoming issues: [ISSUE_TYPES]. Maintainers and time available: [MAINTAINERS_AND_TIME]. Labels in use: [CURRENT_LABELS]. Define a triage rotation, a label set (type, priority, status, good first issue) with definitions, a decision tree for new issues (reproducible bug, feature request, question, duplicate, out of scope), response templates of under 60 words for each decision, and a service target (first response within a number of days). Include a monthly stale-issue process with a polite closing message and a way to thank contributors. Provide a metrics table (open issues, median age, first response time) with the arithmetic. Add a code of conduct reminder and how to handle difficult comments. GitHub features such as issue forms, templates and automation vary; mark them [VERIFY]. Add a worked rotation for four maintainers over a month, a median-age calculation (ages 3, 5, 9, 12, 40 days give a median of 9), and two response templates in full: one for a reproducible bug and one for an out-of-scope request that stays kind and suggests alternatives.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.