|
| 1 | +# AI Contribution Guidelines |
| 2 | + |
| 3 | +This document defines rules for contributions where an AI system is the primary author of the code (i.e., most of the pull request was generated by AI). |
| 4 | +It applies to all Coder repositories and is a supplement to the [existing contributing guidelines](./CONTRIBUTING.md), not a replacement. |
| 5 | + |
| 6 | +For minor AI-assisted edits, suggestions, or completions where the human contributor is clearly the primary author, these rules do not apply — standard contributing guidelines are sufficient. |
| 7 | + |
| 8 | +## Disclosure |
| 9 | + |
| 10 | +Contributors must **disclose AI involvement** in the pull request description whenever these guidelines apply. |
| 11 | + |
| 12 | +## Human Ownership & Attribution |
| 13 | + |
| 14 | +- All pull requests must be opened under **user accounts linked to a human**, and not an application ("bot account"). |
| 15 | +- Contributors are personally accountable for the content of their PRs, regardless of how it was generated. |
| 16 | + |
| 17 | +## Verification & Evidence |
| 18 | + |
| 19 | +All AI-assisted contributions require **manual verification**. |
| 20 | +Contributions without verification evidence will be rejected. |
| 21 | + |
| 22 | +- Test your changes yourself. Don’t assume AI is correct. |
| 23 | +- Provide screenshots showing that the change works as intended. |
| 24 | + - For visual/UI changes: include before/after screenshots. |
| 25 | + - For CLI or backend changes: include terminal or api output. |
| 26 | + |
| 27 | +## Why These Rules Exist |
| 28 | + |
| 29 | +Traditionally, maintainers assumed that producing a pull request required more effort than reviewing it. |
| 30 | +With AI-assisted tools, the balance has shifted: generating code is often faster than reviewing it. |
| 31 | + |
| 32 | +Our guidelines exist to safeguard maintainers’ time, uphold contributor accountability, and preserve the overall quality of the project. |
0 commit comments