Thanks for your interest in contributing! Golems is open source under Apache 2.0.

git clone https://github.com/EtanHey/golems.git
cd golems
bun install

1. Fork the repo and create a branch from master
2. Write tests first when adding new functionality
3. Run tests before pushing: bun test
4. Keep commits focused — one logical change per commit, conventional format (feat:, fix:, docs:)
5. Open a PR against master

1. Create a PR with a clear description of what and why
2. Tests must pass — CI runs automatically
3. CodeRabbit reviews every PR automatically:
   • Fix CRITICAL/HIGH issues before merge
   • MEDIUM issues are judgment calls
   • Style-only comments can be skipped with rationale
4. PRs are squash-merged

We use a vouching system for new contributors, inspired by the t3-oss community:

• First PR? An existing contributor or maintainer reviews and vouches for you
• Vouched contributors get faster review cycles on subsequent PRs
• No CLA required — your contributions are licensed under Apache 2.0 by submitting them
• Add Vouched-by: @username to your PR description if someone invited you

This project uses AI coding tools extensively. When AI agents contribute code:

• Add Co-Authored-By: <agent> <[email protected]> to commit messages
• AI-generated code goes through the same review process as human code
• No distinction in quality standards — all code must pass tests and review

• TypeScript for all new code
• No any types — use proper interfaces
• Tests live next to source files: foo.ts has foo.test.ts
• Use @golems/shared for Supabase, LLM, and notification utilities

Open an issue with: what you expected, what happened, steps to reproduce, and your environment (OS, Bun version).

By contributing, you agree that your contributions will be licensed under the Apache License, Version 2.0.