返回提示词目录第 1319 页

筛选首次开源贡献项目与议题

结合技术背景筛选活跃项目和适合入门的议题,提供认领沟通草稿与停滞时的应对步骤。

完整提示词

<context>
Most first contributions fail before any code is written, because of the project and issue chosen. People pick a famous project where starter issues are claimed within minutes and outside pull requests wait months, when a mid-sized, active project they already use would review them in days. They start on an issue nobody confirmed is wanted, one already assigned, or one whose "good first issue" label is two years stale. They post "can I take this?" under fifteen identical comments, or go silent after claiming an issue so others are blocked. The highest-value first contributions are often not code: a minimal reproduction for an open bug, a docs fix for something you tripped over yourself, a missing test. Maintainers are mostly volunteers; a contributor who asks one specific question, says what they plan to do and keeps them updated gets help. Many projects now reject unreviewed AI-generated pull requests, and contributors are expected to understand and stand behind every line they submit. This prompt covers choosing and engaging; the git and pull request mechanics belong to the next step.

Background:
<background>
{{background}}
</background>
{{#candidate}}
<candidate>
{{candidate}}
</candidate>
{{/candidate}}
</context>

<task>
1. Where to look: from the person's own stack, the kinds of projects to consider (libraries and tools they already use and have hit rough edges in, mid-sized and active), and where to find their starter work (the project's issue labels, docs issues, open bugs without a reproduction). Do not name specific projects as currently welcoming unless the user gave them.
2. Check the project: a five-minute check before investing time: outside pull requests merged in the last few months and how long their first review took, a CONTRIBUTING file, a code of conduct, a sign-off or CLA requirement, a policy on AI-assisted contributions, and whether maintainers reply to newcomers kindly. Say which signals rule a project out.
3. Pick the issue: what makes a good first issue (small, clearly described, confirmed as wanted, not assigned, recent activity), how to spot a contested or stale one, and the non-code alternatives.{{#candidate}} Judge the candidate given against these points and say plainly whether to take it.{{/candidate}}
4. Talk to the maintainers: a short draft comment to claim or ask about the issue, saying what you plan to do and asking one specific question; when to ask in the issue versus the project's chat; and how to post a progress update or hand the issue back if you cannot finish.
5. If it stalls: how long to wait before one polite nudge (state the person should read the project's stated response times first), what to do if the issue is taken by someone else, and how to take a decline without arguing.
6. Next step: once the issue is agreed, hand over to the fork, branch, commit, sign-off and pull request mechanics (the `open-first-pull-request-to-project` prompt covers them), with the one or two project rules to note before starting.
</task>

<constraints>
- Do not invent project policies, maintainers, label names or response times. Tell the person to read the project's own files.
- Do not recommend submitting AI-generated code the person cannot explain, or mass-opening trivial pull requests for a contribution count.
- Do not walk through git commands or the pull request itself; point to the next step instead.
- Keep the plan sized to the time the person said they have.
- Ask one question first if the background does not say which language or tools the person uses.
</constraints>

<output_format>
Use the contract's section headings in order. Each section as short numbered steps or a checklist. Include the claim comment and the progress or hand-back update as fenced drafts the person fills in.
</output_format>

可替换内容

  • {{background}}
  • {{#candidate}}
  • {{candidate}}
  • {{/candidate}}

分类与标签

编程开发、开源贡献、新手入门、议题筛选、维护者沟通

前往 AI 图片创作