Contributor Role

When a bounty is posted, the AI opens a Pull Request with a first-pass solution. As a Contributor, you take that code and make it production-ready before it goes to a Reviewer.

See Bounties Github Board

No approval needed — anyone can contribute. Find an open bounty, claim it, and get to work.

Contributor and Reviewer must be different people on the same bounty.

---

The Process

• Find an issue labeled GoodBounties - <tier> in Ready-For-Assignment status

• Comment to claim it — e.g. "I'd like to contribute to this. ETA: 2–3 days"

• Check out the AI's branch locally and test it — do not just read the diff

• Review against the issue requirements — does the solution actually solve the problem?

• Fix errors — don't just comment, make the changes needed

• Check for: logic errors, security issues, missing tests, code style, codebase consistency

• Verify the PR has a proper description, tags the right issue, and clearly explains what's included

• If UI is involved, add demo videos or screenshots (desktop + mobile)

• Once done, post in the goodbuilders channel to request a Reviewer

---

Checklist Before Handing Off

• Does the solution actually solve what the issue describes?

• Are there edge cases or error states not handled?

• Does the code follow existing patterns and conventions in the repo?

• Are there any TypeScript typing issues or linting failures?

• For UI changes — does it work on both desktop and mobile?

• Is anything over-engineered or unnecessarily complex?

• Are existing helpers/components reused where they could be?

• All fixes applied, not just commented on

---

Tips

• Read the issue carefully before looking at the code — understand the intent first

• Run the changes locally; don't just read the diff, test it

• Check edge cases the AI may have missed (error states, empty inputs, mobile views)

• Ask questions early if the scope or approach isn't clear — on the issue or in the Builders Telegram

---

Timelines

• Begin work within 2–3 days of claiming

• Share progress at least every 3 days; draft PRs are fine for visibility

• If no update or response after 3 days, the issue may be unassigned

---

Ground Rules

• Do not resolve comments left by the maintainer or AI — reply with what you changed, and let them resolve it

• You may use AI tools to assist, but the judgment and fixes must be yours