GitHub Issue Triage Replies and Close Reasons Library
Write kind, clear replies for common situations.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Write a library of issue replies for GitHub. Project type: [PROJECT_TYPE]. Common situations: [SITUATIONS]. Tone: [TONE]. Policies (support questions, security reports, feature requests): [POLICIES]. Write a reply for each situation, each under 80 words, polite and specific, with placeholders and the label to apply: thanks and need more information, cannot reproduce, duplicate, usage question redirected, feature request acknowledged or declined with reasons, security report redirected to the private route without discussing details publicly, stale and closing, fixed in a release, and welcome to a first-time contributor. Model reply for needs more information: 'Thanks for reporting this. To help us reproduce it, could you share the version you are using, the steps you took, what you expected and what happened instead? If you can remove private details and paste any error text, that helps most.' Stale policy: after 14 days without a reply, a friendly reminder; after 30 more, close with a note that the issue can be reopened with new information. Tone rules: assume good faith, avoid jargon, explain next steps, and make people feel heard even when the answer is no. Add a short guide on when not to use a template.
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.