Scope: whole repository.
This repository allows coding agents to help with code review and pull-request preparation.
- Run formatting/lint/tests relevant to changed files before proposing a PR.
- Keep changes minimal and focused; avoid unrelated refactors.
- Update documentation/examples when behavior or APIs change.
- Include risk notes and rollback considerations for non-trivial changes.
- Title format:
<area>: <short summary>(e.g.,rl: fix reward normalization bug). - PR body should include:
- What changed
- Why it changed
- How it was tested (commands + results)
- Any known limitations
- Prefer clear, typed, and well-documented Python.
- Keep public interfaces backward compatible unless explicitly intended.
- Add or update tests for bug fixes and new features when feasible.