- Before modifying files under
docs/, readdocs/AGENTS.md.
- Follow
CONTRIBUTING.mdfor PR title prefixes, RFC expectations, and contribution workflow. - Before opening a PR for nontrivial work, check whether an existing issue or open PR already covers the same change. If the work overlaps, explain the difference instead of duplicating it.
- Do not open low-value busywork PRs for isolated typo, style, or mechanical changes unless they are part of a substantive requested change.
- Use
.github/pull_request_template.mdwhen preparing a PR, and fill in the relevant sections for description, module, type of change, testing, checklist, and AI assistance disclosure. - For AI-assisted changes, make sure the human submitter has reviewed every changed line and can defend the change end-to-end.
- Before handoff, run pre-commit on the files touched by the change when the
toolchain is available (see
CONTRIBUTING.mdfor the PR-scopedpre-commit run --files ...command). Do not usepre-commit run --all-filesfor routine PRs; if it rewrites unrelated files, leave those edits out of the PR. - Keep PRs lean: review
git diffbefore staging, and include only changes required for the requested task.