开源项目问题回复起草
针对使用疑问、越界需求和催更等问题,起草维护者回复并列出标签与后续处理动作。
完整提示词
<context>
Maintainers burn out on the issues that are not bugs: usage questions in the bug tracker, feature requests outside the project's scope, "any update?" pings, demands for a release date, rude or entitled reports, and reports that never come back with the information asked for. Replies go wrong in two directions: too soft (the issue stays open forever and sets an expectation the maintainer cannot meet) or too curt (the person feels dismissed and the thread escalates). A good reply thanks once, says what will and will not happen, gives the person a useful next step, and closes or labels the issue so the tracker stays honest. Maintainers are volunteers or have limited time; replies should protect that time without apologising for it. This is for drafting the replies that are hard to write, one issue or a handful at a time; sorting and labelling a whole backlog is a triage job.
</context>
<task>
<issues>
{{issues}}
</issues>
{{#project_policies}}
<project_policies>
{{project_policies}}
</project_policies>
{{/project_policies}}
1. Classify each issue: usage question, duplicate, needs-info, stale needs-info, out-of-scope feature request, in-scope request without capacity, ETA or "+1" ping, hostile or entitled report, security report filed publicly, or a real bug hidden behind any of these.
2. Look for the real bug first: if a rude or vague report contains a reproducible defect, treat the defect seriously and the tone separately.
3. Decide the action: answer and close, redirect (to the discussion forum or support channel), close as duplicate (link the original), ask for specific information with a deadline, close as stale with an invitation to reopen, close as won't-do with the reason and an alternative (plugin, fork, another tool), keep open with "help wanted" and a pointer to where a contribution would start, or hide or lock under the code of conduct.
4. Draft each reply:
- at most about 120 words, plain and warm, no sarcasm, no apology for having limits;
- for questions: the answer or the link, then where such questions go next time;
- for needs-info: a numbered list of exactly what is needed (version, minimal reproduction, logs) and what happens if it does not arrive by a date;
- for out-of-scope requests: the scope reason in one sentence, an alternative, and no "maybe later" unless it is true;
- for ETA pings: what is known, that there is no date if there is none, and how the person can help (test a branch, fund, contribute);
- for hostile messages: acknowledge the frustration in one line, restate the facts, set the boundary with a link to the code of conduct, and do not mirror the tone; for abuse or repeated violations, recommend moderation instead of a reply;
- for a public security report: thank them, ask them to use the private channel, and suggest hiding the details.
5. Give each issue a label set and the next action for the maintainer.
</task>
<constraints>
- Do not promise fixes, dates or releases the maintainer has not confirmed.
- Use only policies, links and channels given; otherwise use placeholders such as [DISCUSSIONS LINK] and list them.
- Do not invent technical answers; if the answer is unknown, say what the maintainer needs to check.
- Never repeat personal data, tokens or exploit details from the issue in the reply.
</constraints>
<output_format>
## Replies
Per issue: a heading with the issue title, the type, then the reply in a quote block, then "Labels:" and "Action:".
## Summary table
Table: issue, type, action, labels, follow-up date if any.
</output_format>可替换内容
- {{issues}}
- {{#project_policies}}
- {{project_policies}}
- {{/project_policies}}
- [DISCUSSIONS LINK]
分类与标签
编程开发、开源维护、问题追踪、社区沟通