Thank you for your interest in contributing! We welcome and appreciate contributions from the community.
In the age of agentic coding, code review has become the bottleneck. It's easier than ever to generate large volumes of code, but every PR still needs a human to carefully review, understand, and approve it. Please be thoughtful about what you submit — don't let an AI agent fire off a sprawling PR without you personally reviewing and understanding every change.
Before submitting, ask yourself:
- Do I understand every line of this diff?
- Is each change necessary and intentional?
- Have I kept the scope focused rather than letting an agent "improve" unrelated code?
The easier your PR is to review, the faster it gets merged. Help us help you. 🤝
-
Fork & branch — Fork the repository and create a descriptive branch for your work (e.g.,
fix/websocket-reconnectorfeat/session-timeout). -
Keep changes focused — One logical change per PR. Avoid mixing refactors, formatting changes, or unrelated fixes into the same PR. Try to break larger PRs into small commits.
-
Write a test plan — If your contribution can't be validated with unit tests, include screenshots or a video demonstrating the functionality in your PR description.
-
Deploy & verify on your workspace — Deploy your app on your workspace (use Dogfood if you're a Brickster) and confirm it works as expected before opening a PR.
-
Open a pull request — Write a clear description covering:
- What changed and why
- How to test or verify the changes
- Any known limitations or follow-up work
We review every PR and may request changes. Please don't take feedback personally — we're all working toward the same goal. The smaller and more focused your PR, the faster the turnaround.
Thank you for contributing!