Contribution Guide

For the full contribution guide, see CONTRIBUTING.md in the repository root. This page is a summary for the documentation site.

Thank you for your interest in River Review. We accept Pull Requests and Issues according to the following policies.

How we evolve this OSS project

We evaluate proposals against local evidence and external knowledge. Contributions may simplify or remove an unhelpful step, not only add new skills or checks. See our Practice Evolution policy for adopt, adapt, transform, and defer decisions. Existing submission, review, and CI rules still apply.

PR Basic Policy

• Limit one PR to one purpose. Split multiple changes.
• Clearly state what changed and why in the title and description.
• Include links to related files if affecting other docs or code.

Code and Documents

• Write documents in Japanese (Japanese version is Source of Truth). If preparing English version, add .en.md with same name; prioritize Japanese version if content diverges.
• Provide English examples for technical terms if needed.
• Follow the style guide (See WRITING_GUIDE.md).
• Record in PR if adding/changing labels or checks for review.

Issue Reporting

• Register bug reports and feature requests as Issues.
• Specifically write reproduction steps, expected results, and actual results.

Create Issues from templates (Issues -> New issue, or issues/new/choose).

Refer to pages/guides/governance/issue-management.md for label guidelines and triage policy.

Thank you for your cooperation!