Skip to content

docs: Add documentation review guidance#3495

Open
kfelternv wants to merge 6 commits into
NVIDIA:mainfrom
kfelternv:codex/docs-review-rules
Open

docs: Add documentation review guidance#3495
kfelternv wants to merge 6 commits into
NVIDIA:mainfrom
kfelternv:codex/docs-review-rules

Conversation

@kfelternv

Copy link
Copy Markdown
Contributor

No description provided.

@copy-pr-bot

copy-pr-bot Bot commented Jul 14, 2026

Copy link
Copy Markdown

Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually.

Contributors can view more details about this message here.

@kfelternv
kfelternv requested a review from polarweasel July 14, 2026 18:05
@coderabbitai

coderabbitai Bot commented Jul 14, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

Summary by CodeRabbit

  • Documentation
    • Expanded documentation review guidance with checks for interfaces, generated content, workflows, metrics, cross-page consistency, redirects, releases, version boundaries, and rendered output.
    • Updated technology stack formatting for improved readability.
    • Replaced the outdated further-reading reference with the architecture overview.
    • Documentation contributors now have clearer, more comprehensive validation steps for keeping published content accurate and consistent.

Walkthrough

AGENTS.md updates repository formatting guidance, expands the Documentation review checklist with code-evidence verification requirements, and replaces a Further Reading reference.

Changes

Documentation guidance

Layer / File(s) Summary
Documentation review guidance and formatting
AGENTS.md
Adds checks for interfaces, generated artifacts, workflow parity, metrics, cross-page consistency, redirects, release notes, version boundaries, and rendered output; updates section formatting and the Further Reading link.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Possibly related PRs

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name Status Explanation Resolution
Description check ❓ Inconclusive No pull request description was provided, so its relevance cannot be assessed. Add a brief description that explains the intent and scope of the documentation guidance update.
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly summarizes the main change: adding documentation review guidance.
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.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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

@polarweasel polarweasel 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.

Added some changes and some questions...

Comment thread AGENTS.md Outdated
Comment thread AGENTS.md Outdated
Comment thread AGENTS.md Outdated
Comment thread AGENTS.md
Comment thread AGENTS.md Outdated
Comment thread AGENTS.md Outdated
Comment thread AGENTS.md
Comment thread AGENTS.md Outdated
Comment thread AGENTS.md Outdated
@kfelternv
kfelternv marked this pull request as ready for review July 18, 2026 02:08
@kfelternv
kfelternv requested a review from a team as a code owner July 18, 2026 02:08
@kfelternv
kfelternv requested a review from polarweasel July 18, 2026 02:09

@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.

Actionable comments posted: 3

🤖 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.

Inline comments:
In `@AGENTS.md`:
- Around line 274-275: Update the documentation guidance near the public-page
requirements so redirects in fern/docs.yml are required only when public paths
are moved or removed, not for ordinary content changes at an unchanged path.
Keep the docs/index.yml requirement for new or moved public pages unchanged.
- Around line 296-303: Update the command examples in the documentation workflow
section of AGENTS.md to avoid raw angle-bracket placeholders that shells
interpret as redirection. Replace them with realistic concrete values or show
safely quoted variable definitions before using them, while preserving the
existing rumdl and Fern command behavior.
- Around line 226-227: Update the contract verification guidance in AGENTS.md to
require real --help comparison only for changed CLI examples. For APIs,
configuration, environment variables, and states, require appropriate validation
through schemas, handlers, or exercised outputs instead, while preserving
coverage of all changed interface types.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: cb95787f-da8f-4dc2-99cf-176b86aa4fcb

📥 Commits

Reviewing files that changed from the base of the PR and between 536bb26 and 7f8c93e.

📒 Files selected for processing (1)
  • AGENTS.md

Comment thread AGENTS.md
Comment on lines +226 to +227
- Exercise each changed example at the PR revision on an authorized local or
test target and compare it with real `--help` output.

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.

🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win

Limit --help verification to CLI examples.

The surrounding contract list also covers APIs, config, environment variables, and states, for which --help output is not applicable. Require --help comparison for CLI examples, and use schemas, handlers, or exercised output for other interfaces.

As per coding guidelines, interface-contract checks must cover non-CLI inputs as well as commands.

🤖 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.md` around lines 226 - 227, Update the contract verification guidance
in AGENTS.md to require real --help comparison only for changed CLI examples.
For APIs, configuration, environment variables, and states, require appropriate
validation through schemas, handlers, or exercised outputs instead, while
preserving coverage of all changed interface types.

Source: Coding guidelines

Comment thread AGENTS.md
Comment on lines +274 to +275
- New or moved public pages must be present in `docs/index.yml`, and changed
public paths need redirects in `fern/docs.yml`.

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.

🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win

Require redirects only for moved or removed public paths.

“Changed public paths need redirects” is overbroad: content changes at an existing path do not require redirects. Fern’s missing-redirects check concerns pages removed or moved without preserving their previous URLs. (buildwithfern.com)

🤖 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.md` around lines 274 - 275, Update the documentation guidance near the
public-page requirements so redirects in fern/docs.yml are required only when
public paths are moved or removed, not for ordinary content changes at an
unchanged path. Keep the docs/index.yml requirement for new or moved public
pages unchanged.

Comment thread AGENTS.md
Comment on lines +296 to +303
- Run `rumdl check --config docs/.rumdl.toml <changed-markdown-files>` and fail
on every finding.
- For Fern-published pages, inspect the CI-created PR preview. A local
`fern docs dev` preview works without a Fern token, but does not apply the
global `nvidia` theme without one.
- If a hosted preview must be created manually, run
`fern generate --docs --preview --id <stable-id>`, then delete it after
review with `fern docs preview delete --id <stable-id>`.

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.

🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win

Make shell placeholders safe to copy.

Values such as <changed-markdown-files> and <stable-id> are interpreted by the shell as redirection syntax when copied literally. Use concrete examples or define quoted variables before invoking these commands.

As per path instructions, Markdown commands and examples must be realistic and safe.

🤖 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.md` around lines 296 - 303, Update the command examples in the
documentation workflow section of AGENTS.md to avoid raw angle-bracket
placeholders that shells interpret as redirection. Replace them with realistic
concrete values or show safely quoted variable definitions before using them,
while preserving the existing rumdl and Fern command behavior.

Source: Path instructions

@github-actions

Copy link
Copy Markdown

🔍 Container Scan Summary

Service Total Critical High Medium Low Other
boot-artifacts-aarch64 3 0 0 3 0 0
boot-artifacts-x86_64 3 0 0 3 0 0
forge-admin-cli-x86_64 259 16 29 79 7 128
machine-validation-runner 532 39 113 184 15 181
machine_validation 532 39 113 184 15 181
machine_validation-aarch64 532 39 113 184 15 181
nvmetal-carbide 532 39 113 184 15 181
TOTAL 2393 172 481 821 67 852

Per-CVE detail lives in the per-service grype-* artifacts (JSON + SARIF). Severity counts only — no CVE IDs published here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants