| # AI Policy | |
| AI-assisted contributions are welcome. We especially appreciate fixes for bugs | |
| you encounter while using pybind11 and features that help you build something | |
| useful. | |
| ## Start with a concrete need | |
| Please explain the problem or use case that motivated your contribution and | |
| who benefits. Include a reproducer or regression test for bug fixes, and discuss | |
| substantial changes with maintainers before implementation. | |
| Please do not submit issues or PRs primarily to collect contribution credit | |
| or demonstrate an agent's capabilities. Keep experiments in automated PR | |
| generation in your own repositories. When working from an issue list, prioritize | |
| a problem whose importance you can explain; avoid batches of unrelated changes. | |
| ## Take responsibility for your contribution | |
| Review and understand what you submit, verify technical claims, and meet the | |
| project's quality, testing, and style standards. Describe your testing and any | |
| limitations. When unsure, use AI tools to build the expertise you need. Stay | |
| involved during review, consider feedback, and be ready to explain your choices. | |
| ## Be transparent about AI assistance | |
| Disclose AI assistance and name the tool and model used. Briefly describe its | |
| role and how you checked the result. Clearly mark AI-generated text in PR | |
| descriptions, issues, and comments. | |
| Only humans can be named as co-authors or certify a commit with a `Signed-off-by` | |
| trailer. You may credit AI assistance with: | |
| ```text | |
| Assisted-by: <harness>:<model> | |
| ``` | |
| ## Keep review manageable | |
| Reviewing a contribution can take much longer than generating it. Please check | |
| for existing issues and PRs and follow the | |
| [two-PR limit for new contributors](.github/CONTRIBUTING.md#pull-requests). | |
| Maintainers may ask you to narrow or prioritize your work, or close submissions | |
| that do not meet these expectations. |