Documentation Conventions

SkillDocs & knowledge

Lets your agent follow NeMo-RL documentation conventions when writing or updating docs and docstrings.

Then ask your AI: use the Documentation Conventions skill

Details

Instructions available. Your AI can read the instructions. Execution depends on the setup they require.

Add it as a step in a pipeline you build on Ahel, or connect Ahel to Claude, ChatGPT, Cursor, Claude Code or Codex and ask your AI to use it.

About this skill

Documentation conventions for NeMo-RL. Covers docs/index.md updates and docstring format. Do NOT use for: bug fixes, test fixes, dependency bumps, refactoring, CI/CD changes, performance tuning, or any task that does not involve writing or updating documentation.

What this skill tells your AI

The instructions your AI receives, as published by nvidia/skills in skills/nemo-rl-docs/SKILL.md and read by Ahel’s review.

Keep docs/index.md Up to Date

When a new markdown doc is added under docs/**/*.md or a markdown file is renamed, ensure that @docs/index.md is updated and the document appears in the most appropriate section.

Docstring Format

Use Google style docstrings for classes and functions. These are parseable by Sphinx.

For interfaces that may be used outside a file, prefer docstrings over comments. Comments should be reserved for code within a function or interfaces local to a file.

Document New Features

When a new feature is added, update or create documentation in the docs/ directory that most closely matches the feature. Look at existing docs to find the best fit — if none exists, create a new doc and add it to @docs/index.md.

Documentation changes are not required for bug fixes or CI-related changes.

Signals

GitHub stars
4k
Forks
434
Last commit
Oct 2026
Advanced
Item type
skill
Key
nemo-rl-docs
Source
github.com/nvidia/skills