review-doc-style
Skill75 starsChanged 2 months agoApache-2.0View on GitHub
Review NeMo Fabric documentation, examples, and docs-heavy changes for NVIDIA technical writing style, terminology, repository accuracy, and current public behavior. Use for documentation reviews and public-facing text changes.
1 other project uses a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- NVIDIA/NeMo-Relayedited, first seen Sep 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- NVIDIA/NeMo-Relay★ 24611% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository25 other files it gives its agents.
- AGENTS.mdAGENTS.md
- check-release-deploymentsSkill
- contribute-adapterSkill
- contribute-apiSkill
- contribute-docsSkill
- create-beta-tagSkill
- create-rc-tagSkill
- create-release-tagSkill
- draft-release-notesSkill
- karpathy-guidelinesSkill
- maintain-ciSkill
- maintain-packagingSkill
- prepare-code-freezeSkill
- prepare-prSkill
- python-testsSkill
- qualify-harborSkill
- small-fixSkill
- update-project-versionSkill
- validate-changeSkill
- code-reviewSkill
- swebench-debuggingSkill
- nemo-fabric-build-adapterSkill
- nemo-fabric-integrateSkill
- alternateSkill
- defaultSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
19 rules. About 0 are common, 11 are distinctive, and 8 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈11
Distinctive · estimate
This author's own choices. Worth a look.
8
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
Use karpathy-guidelines alongside this skill for implementation or review work.
- Distinctive: line 17
Use this skill when reviewing docs-only changes, example-heavy changes, or any public-facing text update that should be checked against …
- Very specific: line 23
Treat all files under docs/reference/api/ as generated output.
- Very specific: line 31
Run just docs to regenerate and validate the API reference after changing a source or generator.
- Very specific: line 39
Do not use Fern site-root paths such as NeMo Fabric overview.
- Very specific: line 41
Use the repository-relative equivalent, such as NeMo Fabric overview.
- Distinctive: line 48
Keep docs aligned with current NeMo Fabric behavior, repo layout, and entry points
- Distinctive: line 53
All other uses of the name can use the shortened form "NeMo Fabric".
- Distinctive: line 60
Check whether entry-point docs also need updates:
- Very specific: line 65
Start with assets/nvidia-style-guide.md, then open only the focused support document needed for the issue under review.
- Distinctive: line 71
Treat these as blocking issues:
- Distinctive: line 103
Voice: Prefer active voice, present tense, short sentences, and plain English.
- Very specific: line 104
Links: Use descriptive anchor text, not bare URLs or weak labels.
- Distinctive: line 110
Terminology: Use consistent terms throughout the document.
- Distinctive: line 111
Dates and time: Avoid ambiguous numeric dates and ordinal dates in body text.
- Distinctive: line 112
Temporal references: Prefer "after" over "once".
- Distinctive: line 117
When performing a docs review, lead with findings and keep them actionable:
- Distinctive: line 130
If no issues are found, say so explicitly and mention any residual risk, such as commands or examples that were not executed.
- Very specific: line 134
Start with the checklist above and assets/nvidia-style-guide.md.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Review Documentation Style
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 when reviewing docs-only changes, example-heavy changes, or any public-facing text update that should be checked against NVIDIA style guidance and NVIDIA NeMo Fabric repo conventions.
Generated API Reference
- Treat all files under
docs/reference/api/as generated output. Do not modify them directly. - For Python API reference changes, update the source docstrings under
sdk/python/nemo-fabric-runtime/src/nemo_fabric/or the generator inscripts/generate_api_docs.sh. - For Rust API reference changes, update the Rust documentation comments under
crates/fabric-core/or the generator inscripts/docs/generate_rust_library_reference.py. - Run
just docsto regenerate and validate the API reference after changing a source or generator.
Documentation Links
- For links between files under
docs/, use paths relative to the source file and include the target file's.mdxextension. These links work in both Fern builds and repository browsers. - Do not use Fern site-root paths such as
[NeMo Fabric overview](/nemo/fabric/about-nemo-fabric/overview). - Use the repository-relative equivalent, such as
[NeMo Fabric overview](../about-nemo-fabric/overview.mdx).
Review Priorities
- Prioritize factual accuracy over copy polish
- Flag stale commands, package names, APIs, bindings, repo paths, or support claims before stylistic issues
- Keep docs aligned with current NeMo Fabric behavior, repo layout, and entry points
- Apply NVIDIA technical-writing guidance where it improves clarity and consistency without watering down technical precision
- For new documentation, use
\nnewline characters only to intentionally start a new paragraph or add space around a code block or section heading. Do not enforce a line length or reformat an entire document; apply this only to newly written text or the paragraph being edited. - The full product name is "NVIDIA NeMo Fabric".
- The first usage of the name (typically in the title and H1 tag) should use the full product name.
- All other uses of the name can use the shortened form "NeMo Fabric".
- The only acceptable usage of "fabric" by itself is when referring to the CLI tool, and these references must be surrounded by back-ticks.
Review Flow
- Identify the changed docs, examples, or public-facing strings.
- Confirm the described behavior is still true in the current repo.
- Check whether entry-point docs also need updates:
README.mddocs/index.yml- Package or crate READMEs
- Adapter and integration READMEs such as
adapters/python/codex/README.mdorintegrations/harbor/README.md
- Start with
assets/nvidia-style-guide.md, then open only the focused support document needed for the issue under review. - Scan for high-signal style issues in headings, links, code formatting, terminology, procedures, and plain-English readability.
- Report findings in severity order with file references and concrete rewrites.
Must-Fix Findings
Treat these as blocking issues:
- Commands, package names, file paths, or APIs are incorrect or stale
- Public behavior changed but the corresponding entry-point docs were not updated
- A doc claims support for a binding, feature, or workflow that the repo no longer provides
- Examples or procedures are likely to fail as written
- User-facing naming is inconsistent with current repo terminology
- MDX top-of-file SPDX comments use HTML comment delimiters instead of
{/* ... */} - Links between files under
docs/use Fern site-root paths instead of repository-relative.mdxpaths - NVIDIA is not capitalized correctly
- Code, commands, paths, or filenames are not formatted as inline code where needed
Should-Fix Findings
Flag these when they materially improve clarity or consistency:
- Headings are not in title case for technical documentation
- Code blocks, tables, or lists are introduced with incomplete lead-in sentences
- Raw URLs or generic link text such as "here" appear in prose
- Passive voice, long sentences, or vague wording bury the action
- Terminology changes within the same document for the same concept
- Procedures are not imperative, not parallel, or too long for one sequence
- "once" is used where "after" is clearer
- "may" is used when the meaning is possibility rather than permission and "can" would be clearer
High-Signal Review Checklist
- Accuracy: Commands, paths, package names, APIs, and binding claims match the current repo.
- Entry points: Top-level docs changed wherever users would naturally look first.
- Headings: Technical docs use title case consistently.
- Voice: Prefer active voice, present tense, short sentences, and plain English.
- Links: Use descriptive anchor text, not bare URLs or weak labels. For links
within
docs/, use repository-relative paths with the.mdxextension. - Formatting: Commands, code elements, expressions, file names, and paths are monospace.
- MDX headers: Top-of-file MDX SPDX comments use
{/*and*/}delimiters. - Procedures: Steps are easy to scan, imperative, and split into smaller tasks when long.
- Examples: Code blocks are introduced by full sentences and match current APIs and build commands.
- Terminology: Use consistent terms throughout the document.
- Dates and time: Avoid ambiguous numeric dates and ordinal dates in body text.
- Temporal references: Prefer "after" over "once".
- Trademarks: For learning-oriented docs, do not force trademark symbols unless the source doc explicitly requires them.
Output Format
When performing a docs review, lead with findings and keep them actionable:
Must fix: incorrect, stale, misleading, or clearly noncompliant issuesShould fix: clarity and consistency issues that materially improve the docNice to have: optional polish only when the review asked for thoroughness
Each finding should include:
- File path and line reference
- What is wrong now
- Why it conflicts with repo or style guidance
- A concrete rewrite or direction
If no issues are found, say so explicitly and mention any residual risk, such as commands or examples that were not executed.
When To Open Style Support Docs
Start with the checklist above and assets/nvidia-style-guide.md. Open support
docs selectively instead of reading every asset for routine reviews.
| Support Doc | Open For |
assets/nvidia-style-technical-docs.md | Headings, links, lists, tables, code examples, procedures, UI references, accessibility, and technical-document formatting. |
assets/nvidia-style-language-mechanics.md | Voice, tone, plain English, active voice, contractions, temporal wording, punctuation, dates, numbers, units, and symbols. |
assets/nvidia-style-brand-terminology.md | NVIDIA capitalization, product names, model names, trademarks, acronyms, titles, legal copy, SEO, and social copy. |
References
README.mddocs/index.ymlassets/nvidia-style-guide.mdassets/nvidia-style-technical-docs.mdassets/nvidia-style-language-mechanics.mdassets/nvidia-style-brand-terminology.md
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

