Skip to content

docs(contributor): streamline create-pr verification - #5396

Merged
cv merged 1 commit into
mainfrom
codex/streamline-create-pr-checks
Jun 13, 2026
Merged

docs(contributor): streamline create-pr verification#5396
cv merged 1 commit into
mainfrom
codex/streamline-create-pr-checks

Conversation

@cv

@cv cv commented Jun 13, 2026

Copy link
Copy Markdown
Collaborator

Summary

Streamline the NemoClaw create-PR workflow so normal commit and push hooks count as verification instead of requiring duplicate full local gates. The updated guidance prefers diff-scoped hook fallback and targeted tests, while preserving docs-build requirements for documentation changes.

Changes

  • Update the nemoclaw-contributor-create-pr skill to treat normal Git hook success as PR verification and use npx prek run --from-ref main --to-ref HEAD only as a fallback.
  • Revise the PR template verification checklist to distinguish hook evidence, targeted tests, and broad full-suite npm test runs.
  • Align root and docs contributor guidance, including AGENTS.md, CONTRIBUTING.md, docs/AGENTS.md, and docs/CONTRIBUTING.md, with the efficient PR process.

Type of Change

  • Code change (feature, bug fix, or refactor)
  • Code change with doc updates
  • Doc only (prose changes, no code sample modifications)
  • Doc only (includes code sample changes)

Verification

  • Git hooks passed during commit and push, or npx prek run --from-ref main --to-ref HEAD passes
  • Targeted tests pass for changed behavior
  • Full npm test passes (broad runtime changes only)
  • Tests added or updated for new or changed behavior
  • No secrets, API keys, or credentials committed
  • Docs updated for user-facing behavior changes
  • npm run docs builds without warnings (doc changes only)
  • Doc pages follow the style guide (doc changes only)
  • New doc pages include SPDX header and frontmatter (new pages only)

Signed-off-by: Carlos Villela cvillela@nvidia.com

Summary by CodeRabbit

  • Documentation
    • Updated PR verification guidance across contributor documentation, clarifying when to rely on Git hooks versus targeted scoped checks
    • Refined doc-only PR procedures to avoid unnecessary full test suite runs
    • Updated PR template verification checklist with specific requirements for different change types
    • Improved fallback verification guidance when hooks are unavailable

@cv cv self-assigned this Jun 13, 2026
@github-actions

Copy link
Copy Markdown
Contributor

@github-actions

Copy link
Copy Markdown
Contributor

E2E Advisor Recommendation

Required E2E: None
Optional E2E: None

Workflow run

Full advisor summary

E2E Recommendation Advisor

Base: origin/main
Head: HEAD
Confidence: high

Required E2E

  • None. No E2E is recommended. The changes are documentation, PR template, and contributor-agent guidance updates only. They do not modify NemoClaw runtime code, installer/onboarding behavior, sandbox lifecycle, credentials, security boundaries, network policy, inference routing, deployment, or real assistant user flows.

Optional E2E

  • None.

New E2E recommendations

  • None.

@github-actions

Copy link
Copy Markdown
Contributor

Vitest E2E Scenario Recommendation

Required Vitest E2E scenarios: None
Optional Vitest E2E scenarios: None

Workflow run

Full Vitest E2E advisor summary

Vitest E2E Scenario Advisor

Base: origin/main
Head: HEAD
Confidence: high

Required Vitest E2E scenarios

  • None. No Vitest E2E scenario dispatch is recommended because this PR only changes contributor documentation, PR template text, and agent guidance files; it does not touch test/e2e-scenario/, .github/workflows/e2e-vitest-scenarios.yaml, or other Vitest scenario-relevant behavior.

Optional Vitest E2E scenarios

  • None.

Relevant changed files

  • None.

@coderabbitai

coderabbitai Bot commented Jun 13, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

📝 Walkthrough

Walkthrough

This PR updates contributor guidance across six documentation files to streamline PR verification workflows. The changes consolidate around Git hooks (pre-commit, commit-msg, pre-push) as the primary verification mechanism, with a narrower diff-scoped fallback command (npx prek run --from-ref main --to-ref HEAD) when hooks are skipped or unavailable, replacing previous blanket full-suite re-runs.

Changes

PR Verification Workflow Guidance

Layer / File(s) Summary
Skill documentation: verification workflow redefinition
.agents/skills/nemoclaw-contributor-create-pr/SKILL.md
Step 2 guidance reworked to prefer hook evidence and use diff-scoped fallback; Verification checklist updated to confirm hooks passed or fallback prek succeeds, targeted tests pass, and full npm test passes only for broad runtime changes; instructions and common mistakes clarified to discourage rerunning hook-covered checks and avoid full test suites for doc-only changes.
PR template checklist
.github/PULL_REQUEST_TEMPLATE.md
Checklist updated to match skill guidance: Git hooks/prek diff-range confirmation, targeted test pass, and full npm test pass; removed prior --all-files requirement.
Contributor documentation updates
AGENTS.md, CONTRIBUTING.md
Updated to reflect normal hook-first workflow with explicit npx prek run --from-ref main --to-ref HEAD fallback when hooks are skipped/unavailable; refined targeted test selection and conditional doc-build guidance.
Doc-only PR verification guidance
docs/AGENTS.md, docs/CONTRIBUTING.md
Shifted from pre-submit full-suite runs to hooks-first workflow with narrowed diff-scoped fallback and conditional targeted test execution for code/behavior changes in doc PRs.

Possibly Related PRs

  • NVIDIA/NemoClaw#5368: Updates documentation workflow and verification guidance (AGENTS.md, doc-only instructions, npx prek run fallback behavior) for the same PR/doc verification process.

Suggested Labels

area: docs, area: skills

Estimated Code Review Effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐰 A rabbit hops through docs so clear,
Hooks now lead, no fear!
Skip the full-suite's lengthy task—
Diff-scoped checks, that's all we ask.
Simpler verification, swift and keen,
The cleanest workflow ever seen! ✨

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and specifically describes the main change: streamlining PR verification in contributor documentation by shifting from full local gate requirements to Git hook-based verification with targeted fallbacks.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch codex/streamline-create-pr-checks

Comment @coderabbitai help to get the list of available commands and usage tips.

@github-actions

Copy link
Copy Markdown
Contributor

PR Review Advisor

Findings: 0 needs attention, 0 worth checking, 0 nice ideas
Top item: No actionable findings

Workflow run details

This is an automated advisory review. A human maintainer must make the final merge decision.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
.agents/skills/nemoclaw-contributor-create-pr/SKILL.md (1)

1-4: ⚠️ Potential issue | 🔴 Critical | ⚡ Quick win

Missing SPDX license header.

The file must include an SPDX license header in HTML comments after the YAML frontmatter. Per coding guidelines, every .md file requires the header.

🛡️ Proposed fix
 ---
 name: nemoclaw-contributor-create-pr
 description: Create GitHub pull requests that follow the NemoClaw PR template. Use when the user wants to create a new PR, submit code for review, open a pull request, or push changes for review. Trigger keywords - create PR, pull request, new PR, submit for review, open PR, push for review.
 ---
+
+<!-- SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved. -->
+<!-- SPDX-License-Identifier: Apache-2.0 -->

 # Create GitHub Pull Request
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.agents/skills/nemoclaw-contributor-create-pr/SKILL.md around lines 1 - 4,
Add an SPDX license header as an HTML comment immediately after the YAML
frontmatter in the .md file; in nemoclaw-contributor-create-pr/SKILL.md insert a
line like <!-- SPDX-License-Identifier: <LICENSE-ID> --> (replacing <LICENSE-ID>
with the project's chosen SPDX identifier) on the first line after the closing
--- so the file has the required SPDX header.

Source: Coding guidelines

🧹 Nitpick comments (2)
.github/PULL_REQUEST_TEMPLATE.md (1)

1-2: 💤 Low value

Add SPDX license header for consistency.

For consistency with other markdown files in the root (AGENTS.md, CONTRIBUTING.md), add an SPDX header comment before the template content.

💡 Proposed fix
+<!-- SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved. -->
+<!-- SPDX-License-Identifier: Apache-2.0 -->
 <!-- markdownlint-disable MD041 -->
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.github/PULL_REQUEST_TEMPLATE.md around lines 1 - 2, Add an SPDX license
header comment at the top of the pull request template by inserting a
single-line SPDX identifier (e.g., <!-- SPDX-License-Identifier: MIT -->)
immediately before the existing markdown content so the template matches other
root markdown files; update .github/PULL_REQUEST_TEMPLATE.md by placing the SPDX
comment above the existing "<!-- markdownlint-disable MD041 -->" line.
.agents/skills/nemoclaw-contributor-create-pr/SKILL.md (1)

222-224: 💤 Low value

Reduce repetition of "Do not" at sentence starts.

Three successive sentences begin with "Do not," which LanguageTool flags as repetitive. Consider restructuring one or two to improve flow.

💡 Suggested refactoring
 - **Do not rerun hook-covered checks by default.** Normal commit and push hooks are valid verification. Use `npx prek run --from-ref main --to-ref HEAD` as the fallback when hooks were skipped, missing, or uncertain.
-- **Do not run the full test suite for doc-only changes by default.** Run the docs build instead, and leave `npm test` unchecked unless you actually ran it.
+- **For doc-only changes, skip the full test suite by default.** Run the docs build instead, and leave `npm test` unchecked unless you actually ran it.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.agents/skills/nemoclaw-contributor-create-pr/SKILL.md around lines 222 -
224, Reword the three consecutive bullets that each start with "Do not" to
reduce repetition: change "Do not rerun hook-covered checks by default. Normal
commit and push hooks are valid verification. Use `npx prek run --from-ref main
--to-ref HEAD` as the fallback when hooks were skipped, missing, or uncertain."
into a positive/neutral phrasing like "Avoid rerunning hook-covered checks by
default; use `npx prek run --from-ref main --to-ref HEAD` only when hooks were
skipped, missing, or uncertain," change "Do not run the full test suite for
doc-only changes by default. Run the docs build instead, and leave `npm test`
unchecked unless you actually ran it." into "For doc-only changes, run the docs
build instead of the full test suite and leave `npm test` unchecked unless you
actually ran it," and change "Do not forget the DCO sign-off. CI will reject the
PR without it." into "Remember to include the DCO sign-off; CI will reject the
PR without it." Update the three list items accordingly.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Outside diff comments:
In @.agents/skills/nemoclaw-contributor-create-pr/SKILL.md:
- Around line 1-4: Add an SPDX license header as an HTML comment immediately
after the YAML frontmatter in the .md file; in
nemoclaw-contributor-create-pr/SKILL.md insert a line like <!--
SPDX-License-Identifier: <LICENSE-ID> --> (replacing <LICENSE-ID> with the
project's chosen SPDX identifier) on the first line after the closing --- so the
file has the required SPDX header.

---

Nitpick comments:
In @.agents/skills/nemoclaw-contributor-create-pr/SKILL.md:
- Around line 222-224: Reword the three consecutive bullets that each start with
"Do not" to reduce repetition: change "Do not rerun hook-covered checks by
default. Normal commit and push hooks are valid verification. Use `npx prek run
--from-ref main --to-ref HEAD` as the fallback when hooks were skipped, missing,
or uncertain." into a positive/neutral phrasing like "Avoid rerunning
hook-covered checks by default; use `npx prek run --from-ref main --to-ref HEAD`
only when hooks were skipped, missing, or uncertain," change "Do not run the
full test suite for doc-only changes by default. Run the docs build instead, and
leave `npm test` unchecked unless you actually ran it." into "For doc-only
changes, run the docs build instead of the full test suite and leave `npm test`
unchecked unless you actually ran it," and change "Do not forget the DCO
sign-off. CI will reject the PR without it." into "Remember to include the DCO
sign-off; CI will reject the PR without it." Update the three list items
accordingly.

In @.github/PULL_REQUEST_TEMPLATE.md:
- Around line 1-2: Add an SPDX license header comment at the top of the pull
request template by inserting a single-line SPDX identifier (e.g., <!--
SPDX-License-Identifier: MIT -->) immediately before the existing markdown
content so the template matches other root markdown files; update
.github/PULL_REQUEST_TEMPLATE.md by placing the SPDX comment above the existing
"<!-- markdownlint-disable MD041 -->" line.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: d9a1a01c-8087-444a-b995-5aa4fe70c8ff

📥 Commits

Reviewing files that changed from the base of the PR and between 720bee9 and 32b993b.

📒 Files selected for processing (6)
  • .agents/skills/nemoclaw-contributor-create-pr/SKILL.md
  • .github/PULL_REQUEST_TEMPLATE.md
  • AGENTS.md
  • CONTRIBUTING.md
  • docs/AGENTS.md
  • docs/CONTRIBUTING.md

@cv
cv merged commit 37ab3ff into main Jun 13, 2026
42 checks passed
@cv
cv deleted the codex/streamline-create-pr-checks branch June 13, 2026 18:32
@cv cv added the v0.0.65 label Jun 15, 2026
@wscurran wscurran added area: docs Documentation, examples, guides, or docs build chore Build, CI, dependency, or tooling maintenance labels Aug 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area: docs Documentation, examples, guides, or docs build chore Build, CI, dependency, or tooling maintenance

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants