Begin with a seam, not the whole system.
Documentation repairs, accessibility checks, cross-platform tests and synthetic evaluation cases reveal how Rangabot works without requiring a major architecture change.
Browse good first issues ↗Craft one capability well.
Rangabot grows through bounded work, explicit acceptance criteria and evidence. You do not need to understand the entire project to improve one honest part of it.
Core reliability
Conversation, memory, provider recovery, repeatability and honest evaluation are the foundation for every future mastery path.
See open gates →Achievements remembered
Opt-in contributor claims require merged evidence and official approval. Credit remains even if a capability later regresses.
Request a claim ↗Clear, kind review
Challenge claims and architecture without diminishing the person doing the work. Safety and privacy concerns receive priority.
Read the covenant ↗One command to verify
Contributor setup, checks and supported environments are documented in the repository. Ubuntu and Windows CI guard every pull request.
Contribution guide ↗The contribution journey
Discussion becomes evidence.
01Discuss02Choose scope03Build04Validate05Review06Remember