Read CODEOWNERS for component ownership. Review a change against actual consumers, preserved behavior, and appropriate validation. Keep unrelated improvements separate.
Follow the PR template. Keep one
conversation comment beginning with <!-- kumo-pr-change-map -->, account for
every changed file, and link to it from the description. Update that comment
after new commits; keep summaries in the description and rationale in the map.
The PR author or authorized bot must maintain it.
To validate locally:
gh api repos/kumo-ai/kumo/pulls/NUMBER > PR.json
gh api --paginate --slurp repos/kumo-ai/kumo/pulls/NUMBER/files | jq 'add' > FILES.json
gh api --paginate --slurp repos/kumo-ai/kumo/issues/NUMBER/comments | jq 'add' > COMMENTS.json
node .github/scripts/pr-change-table.cjs PR.json FILES.json COMMENTS.jsonThe check validates metadata and file coverage; reviewers assess the design and explanation. New commits and comment changes rerun it using the checker on the default branch.