prepare-pr

# Prepare A PR For NeMo Relay 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 - [ ] Validation results accurately report checks already run and relevant omissions without widening validation solely for PR preparation - [ ] Pull request title follows Conventional Commit style and uses the correct type - [ ] Pull request body follows `.github/pull_request_template.md` - [ ] Breaking changes or renamed surfaces are called out explicitly ## Pull Request Title Use Conventional Commit style for PR titles: ```text <type>: <concise imperative summary> ``` Choose the type from the actual change surface, not from the impact of the review comment or CI outcome. Use `fix` only for an actual user-facing or runtime/product code bug fix. Never use `fix` for changes that are not related to product code behavior, including chores, CI configuration, docs, tests, packaging metadata, generated-output handling, or agent/skill guidance. Common examples: - `ci: update codecov coverage reporting` - `docs: clarify release workflow` - `enhancement: improve...