NVIDIA-NeMo
- 14 skills
- 0 followers
- 6 hours ago last updated
- ▌ Nemo Rl Docs · nvidia-nemo-rl bundleDocumentation 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.
- ▌ Launch Nemo Rl · nvidia-nemo-rl bundlePlaybook for launching, monitoring, stopping, and debugging NeMo-RL recipes on a Kubernetes cluster via the nrl-k8s CLI. Covers ephemeral vs long-lived RayCluster modes, iterating on runs, and debugging hung or failed training jobs.
- ▌ Nemo Rl Auto Research · nvidia-nemo-rl bundleAutonomous NeMo-RL research agent workflow for directed hypothesis testing and open-ended discovery. Guides agents through the full experiment lifecycle: understanding recipes and environments, wiring RL or NeMo-gym runs, launching reproducible baselines and iterations, analyzing results, preserving human oversight, and using git plus TSV logs as the research ledger. Do NOT use for: bug fixes, code review, documentation, refactoring, dependency updates, or single-file changes.
- ▌ Nemo Rl Brev Etiquette · nvidia-nemo-rl bundleBrev instance operating guidance for NeMo-RL agents working in /home/ubuntu/RL with limited workspace disk, a larger /ephemeral volume, and optional /home/ubuntu/RL/.env secrets. Use when running nemo-rl-auto-research campaigns, experiments, training jobs, model or dataset downloads, shared cache-heavy commands, log-producing runs, checkpoint generation, W&B or Hugging Face authenticated workflows, or any workflow that may create large files on Brev.
- ▌ Nemo Rl Session Memory · nvidia-nemo-rl bundleManage durable working-session memory for coding agents. Use when a user asks to preserve or recover agent context across disconnects, VS Code restarts, long-running work, handoffs, or any session where important state should be written periodically under the repo's session directory. Do NOT use for: simple questions, short tasks, one-off commands, linting, or code review.
- ▌ Build And Dependency · nvidia-nemo-rlBuild and dependency management for NeMo-RL. Covers Docker image building and running, uv usage, venv setup, and adding dependencies.
- ▌ Linting And Formatting · nvidia-nemo-rlCode style guidelines for NeMo-RL (Python and shell). Covers naming, indentation, comments, docstrings, reflection avoidance, and uv usage.
- ▌ Contributing · nvidia-nemo-rlContribution conventions for NeMo-RL. Covers PR title format, commit sign-off, and CI triggering.
- ▌ Error Handling · nvidia-nemo-rlError handling guidelines for NeMo-RL. Covers exception specificity, minimal try bodies, and else blocks.
- ▌ Review Pr Team · nvidia-nemo-rlAgent-team-based parallel code review for NVIDIA-NeMo/RL pull requests. Spawns specialized agents (RL expert, submodule experts, bug finder, design reviewer, test agent, devil's advocate, comment reviewer) that coordinate via shared task list and direct messaging. Leader orchestrates, collates ALL findings, and presents to user for approval before posting.
- ▌ Config Conventions · nvidia-nemo-rlConfiguration conventions for NeMo-RL. YAML is the single source of truth for defaults. Covers BaseModel/TypedDict usage, dataclass for internal classes, exemplar YAML updates, and forbidden default patterns.
- ▌ Cicd · nvidia-nemo-rlCI/CD reference for NeMo-RL. Covers GitHub Actions pipeline structure, CI triggering via /ok to test, and CI failure investigation.
- ▌ Testing · nvidia-nemo-rlTesting conventions for NeMo-RL. Covers Ray actor coverage pragmas, nightly test requirements, and recipe naming rules.
- ▌ Copyright · nvidia-nemo-rlNVIDIA copyright header requirements for NeMo-RL. Covers which files need headers and the exact header text.