TechnicalFree
Generate open-source contribution guide
Describe your project and how you like to work, and get a CONTRIBUTING.md covering setup, bug reports, pull requests, code style and conduct.
River's Contribution Guide Generator creates comprehensive CONTRIBUTING.md files for open-source projects. You provide project details, and the AI writes complete guides covering how to contribute, code standards, pull request process, issue templates, and community guidelines. Perfect for open-source maintainers building welcoming contributor communities.
Unlike minimal contribution docs, we create complete guides. The AI understands open-source best practices, creates clear processes, and writes welcoming documentation that encourages contributions while maintaining quality.
This tool is perfect for open-source maintainers, project founders documenting processes, teams standardizing contributions, and developers making projects contributor-friendly.
Building Contributor-Friendly Projects
Great open-source projects make contributing easy and welcoming. Effective contribution guides explain how to get started, outline code standards, document PR process, provide issue templates, and create inclusive communities. Clear CONTRIBUTING.md files reduce friction, increase quality contributions, and build sustainable open-source communities.
How It Works
Provide project info
Enter project name and type
AI generates guide
Creates complete CONTRIBUTING.md
Customize and publish
Add project-specific details, commit to repo
What You Get
- Complete CONTRIBUTING.md file
- Getting started guide for contributors
- Code standards and style guide
- Pull request and issue templates
- Community guidelines
- Development workflow documentation
Common questions
Should I include a code of conduct?
Yes. Code of conduct sets behavioral expectations and makes project welcoming. Use Contributor Covenant (standard template). Link from CONTRIBUTING.md. Shows you care about inclusive community.
How detailed should coding standards be?
Specific enough that contributors know expectations. Link to style guide (Airbnb, Google, etc.) rather than rewriting. Note project-specific conventions. Include linter config so standards are automated.
Should I require issue before every PR?
For bugs and features, yes. Allows discussion before work starts. For typos and small fixes, no issue needed. Balance process with friction. Don't make contributing unnecessarily difficult.
Generate open-source contribution guide
Describe what you need, add any files you have, and your workspace opens with the work already underway.