prepare-pr

# Prepare A PR For NeMo Relay ## Companion Guidance Use `karpathy-guidelines` alongside this skill for implementation or review work. Keep changes scoped, surface assumptions, and define focused validation before editing. Use this skill at the end of a contributor or maintainer change before opening a pull request. Also use it whenever a user asks to create, open, publish, update, or edit a NeMo Relay pull request, pull request description, or PR body. If this repo-local guidance conflicts with generic GitHub publishing, connector, or plugin guidance, this skill wins for PR body format, validation language, and review handoff details. ## Checklist - [ ] Branch scope is coherent and reviewable - [ ] Relevant tests passed under `validate-change` - [ ] Changed files were formatted with the language-native formatter - [ ] Any Rust change ran `just test-rust` - [ ] Any Rust change ran `cargo fmt --all` - [ ] Any Rust change ran `cargo clippy --workspace --all-targets -- -D warnings` - [ ] `crates/core` or `crates/adaptive` changes ran the full language matrix - [ ] Targeted `uv run pre-commit run --files <changed files...>` checks were used during iteration where useful - [ ] `uv run pre-commit run --all-files` passed or issues are understood - [ ] Docs and examples updated for any public behavior changes - [ ] Dependent maintainer or consumer skills updated when code changes affected their APIs, bindings, commands, paths, packaging guidance, or best practices - ...