Agent skill

Doc Reviewer

Reviews recent code changes and checks if documentation needs updates.

Apache-2.0Auto-check passedDevelopment

Install Doc Reviewer

skills CLI

$ npx skills add NVlabs/alpasim --skill doc-reviewer -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install NVlabs/alpasim doc-reviewer --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/NVlabs/alpasim.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.cursor/skills/doc-reviewer .claude/skills/doc-reviewer && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "doc-reviewer" agent skill from https://github.com/NVlabs/alpasim/tree/main/.cursor/skills/doc-reviewer into .claude/skills/doc-reviewer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doc-reviewer", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/NVlabs/alpasim/tree/main/.cursor/skills/doc-reviewer

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add NVlabs/alpasim --skill doc-reviewer -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install NVlabs/alpasim doc-reviewer --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/NVlabs/alpasim.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.cursor/skills/doc-reviewer .agents/skills/doc-reviewer && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "doc-reviewer" agent skill from https://github.com/NVlabs/alpasim/tree/main/.cursor/skills/doc-reviewer into .agents/skills/doc-reviewer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doc-reviewer", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add NVlabs/alpasim --skill doc-reviewer -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install NVlabs/alpasim doc-reviewer --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/NVlabs/alpasim.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.cursor/skills/doc-reviewer .cursor/skills/doc-reviewer && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "doc-reviewer" agent skill from https://github.com/NVlabs/alpasim/tree/main/.cursor/skills/doc-reviewer into .cursor/skills/doc-reviewer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doc-reviewer", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/NVlabs/alpasim.git --path .cursor/skills/doc-reviewer

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add NVlabs/alpasim --skill doc-reviewer -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install NVlabs/alpasim doc-reviewer --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/NVlabs/alpasim.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.cursor/skills/doc-reviewer .gemini/skills/doc-reviewer && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "doc-reviewer" agent skill from https://github.com/NVlabs/alpasim/tree/main/.cursor/skills/doc-reviewer into .gemini/skills/doc-reviewer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doc-reviewer", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install NVlabs/alpasim doc-reviewer

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add NVlabs/alpasim --skill doc-reviewer -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/NVlabs/alpasim.git skills-src && mkdir -p .github/skills && cp -r skills-src/.cursor/skills/doc-reviewer .github/skills/doc-reviewer && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "doc-reviewer" agent skill from https://github.com/NVlabs/alpasim/tree/main/.cursor/skills/doc-reviewer into .github/skills/doc-reviewer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doc-reviewer", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add NVlabs/alpasim --skill doc-reviewer -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install NVlabs/alpasim doc-reviewer --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/NVlabs/alpasim.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.cursor/skills/doc-reviewer .opencode/skills/doc-reviewer && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "doc-reviewer" agent skill from https://github.com/NVlabs/alpasim/tree/main/.cursor/skills/doc-reviewer into .opencode/skills/doc-reviewer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doc-reviewer", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: doc-reviewer
GitHub stars: 1.3k
Token cost: ~1.2k tokens
SKILL.md length: 328 words
Files: 1
Skills in repo: 2
Repo updated: Sep 18, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Reviews recent code changes and checks if documentation needs updates.

Works in 4 steps: Identify Changed Files → Discover and Read All Documentation → Analyze Impact → …
Completing features
SKILL.md covers Quick Start, Workflow, What Triggers Documentation… and Example Session, plus 1 more section
Calls git

What it does

Doc Reviewer is an agent skill from NVlabs/alpasim. Reviews recent code changes and checks if documentation needs updates. Reads all MD files in root and docs/ to identify stale or missing documentation. Use when completing features, before pushing, or when asked to "check docs", "review documentation", or "doc-reviewer".

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development. It works with NVIDIA AI Platform. The repository describes itself as: AlpaSim is an open-source autonomous vehicle simulation platform designed for development and testing of end-to-end AV policies. The licence is Apache-2.0.

When your agent uses it

Completing features
Asked to check docs
Review documentation

Example prompts

“check docs”
“review documentation”
“doc-reviewer”
“/doc-reviewer”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

Identify Changed Files
Discover and Read All Documentation
Analyze Impact
Report Findings

What it can do on your machine

Read from SKILL.md and the folder at commit affc2ea. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Doc Reviewer loads about 1.2k tokens when it runs. Until then it costs about 71 tokens; SKILL.md has 328 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~71
When it runs · the whole SKILL.md, loaded when a task matches: ~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from NVlabs/alpasim at commit affc2ea, republished under its Apache-2.0 licence (© NVlabs). 328 words, ~1,249 tokens.

Download SKILL.mdSave it as .claude/skills/doc-reviewer/SKILL.md (or your agent's skills folder).

name: doc-reviewer
description: Reviews recent code changes and checks if documentation needs updates. Reads all MD files in root and docs/ to identify stale or missing documentation. Use when completing features, before pushing, or when asked to "check docs", "review documentation", or "doc-reviewer".

Documentation Reviewer

Reviews code changes since branching from main and checks all documentation for staleness.

Quick Start

Get the list of changed files since branching from main
Discover and read all documentation files
Analyze which docs are affected by the code changes
Report findings with specific recommendations

Workflow

Step 1: Identify Changed Files

bash

# Find the merge base with main
MERGE_BASE=$(git merge-base HEAD main 2>/dev/null || git merge-base HEAD origin/main)

# Get changed files with stats
git diff --stat $MERGE_BASE HEAD

# Get detailed list
git diff --name-only $MERGE_BASE HEAD

Step 2: Discover and Read All Documentation

Find all markdown files in root and docs/:

bash

# Discover all doc files
ls *.md docs/*.md 2>/dev/null

Read all discovered MD files. The total is typically ~40-50k tokens, well within context limits.

Step 3: Analyze Impact

For each code change, check all documentation for:

Contradictions - Docs describe behavior differently than code now works
Missing features - New functionality not documented anywhere
Stale references - Removed code still mentioned in docs
Outdated examples - Code samples that no longer work
Missing CLI options - New flags or commands not documented
Environment variables - New or changed env vars
Changed paths - File/module paths that moved
Dependency changes - New packages or version requirements
Build/test commands - Changed invocation patterns

Step 4: Report Findings

markdown

## Documentation Review Summary

### Changes Analyzed
- X files changed across Y modules
- Commits: [describe range] since branching from main

### Documentation Status

#### Needs Update (High Priority)
- **[doc-path]**: [specific issue]
  - Code change: [what changed]
  - Doc gap: [what's missing or outdated]
  - Suggested fix: [specific text to add/change]

#### May Need Update (Review Recommended)
- **[doc-path]**: [potential issue]

#### Verified Current
- [List docs that were checked and are still accurate]

### Recommended Actions
1. [Ordered list of suggested documentation updates]

What Triggers Documentation Updates

High-priority (almost always needs doc update):

New public API functions or classes
Changed function signatures or parameters
New CLI commands or options
New environment variables
Changed installation or setup steps
Modified build or test commands
New dependencies
Changed file/directory structure
New services or modules

Medium-priority (often needs doc update):

Internal refactoring that changes module organization
Performance improvements worth noting
Bug fixes that clarify expected behavior
Configuration option changes
New error messages or handling

Low-priority (usually no doc update needed):

Internal implementation details unchanged externally
Test-only changes
Docstring improvements (self-documenting)
Style/formatting changes
Comments

Example Session

User: Review the docs for my recent changes

Agent: Let me check what's changed since you branched from main.

[Runs git diff --stat against merge-base]

Found 8 files changed:
- src/runtime/dispatcher.py (new --parallel-workers option)
- src/wizard/cli.py (added --dry-run flag)
- pyproject.toml (bumped numpy version)

Discovering documentation files...

[Lists *.md and docs/*.md, then reads all of them]

## Documentation Review Summary

### Changes Analyzed
- 8 files changed across runtime/, wizard/, and root config
- Branch: feature/parallel-workers

### Needs Update (High Priority)

1. **docs/TUTORIAL.md**: Missing --dry-run flag
   - Code: wizard/cli.py line 45 adds --dry-run option
   - Gap: CLI options section doesn't mention this flag
   - Fix: Add to "Wizard CLI Options" table:
     `| --dry-run | Validate config without executing |`

2. **AGENTS.md**: Outdated numpy reference
   - Code: pyproject.toml now requires numpy>=2.0
   - Gap: Build section mentions numpy 1.x compatibility
   - Fix: Update dependency note or remove version mention

### Verified Current
- docs/OPERATIONS.md - Already covers topic
- docs/DESIGN.md - Architecture unchanged
- CONTRIBUTING.md - Dev workflow unchanged

Integration Points

Before creating a PR:

Run doc-reviewer to catch missing documentation
Include doc updates in the same PR as code

During code review:

Reviewers can request doc-reviewer check
Ensures docs stay synchronized

Periodic maintenance:

Run against main branch for overall health check
Compare key docs (e.g. DESIGN.md, TUTORIAL.md) against recent commits

Files

Just SKILL.md in .cursor/skills/doc-reviewer of NVlabs/alpasim.

Open the folder on GitHubat commit affc2ea

Compare with similar skills

Doc Reviewer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Doc Reviewer compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Doc Reviewer this skillNVlabs/alpasim	1.3k	—	~1.2k	Automated safety check: Pass	Apache-2.0	22 days ago
LLM Torch Profiler Analysissgl-project/sglang	37k	2 repos	~6.4k	Automated safety check: Pass	Apache-2.0	today
Fla Triton To Gluonfla-org/flash-linear-attention	5.8k	—	~1.6k	Automated safety check: Pass	MIT	today
Megatron-LM Container and Dependency SetupNVIDIA/Megatron-LM	18k	—	~2.6k	Automated safety check: Pass	Apache-2.0	today
Nemoclaw Contributor Update DependenciesNVIDIA/NemoClaw	23k	—	~1.4k	Automated safety check: Pass	Apache-2.0	today
Refactor OpCVCUDA/CV-CUDA	2.7k	—	~1.5k	Automated safety check: Pass	Custom licence	23 days ago

Similar skills

LLM Torch Profiler Analysis
sgl-project/sglang
Unified LLM torch-profiler triage skill for sglang, vllm, TensorRT-LLM, and TokenSpeed.
37k GitHub starsUsed in 2 repos~6.4k tokens
DevelopmentAuto-check passed
Fla Triton To Gluon
fla-org/flash-linear-attention
Port an FLA Triton kernel to Gluon when explicit layouts, asynchronous transfers, or scheduling can address a measured bottleneck.
5.8k GitHub stars~1.6k tokensUpdated today
DevelopmentAuto-check passed
Megatron-LM Container and Dependency Setup
NVIDIA/Megatron-LM
Official
Walks an agent through working inside the Megatron-LM CI container and changing dependencies with uv, so lock files resolve the same locally and in CI.
18k GitHub stars~2.6k tokensUpdated today
DevelopmentAuto-check passed
Nemoclaw Contributor Update Dependencies
NVIDIA/NemoClaw
Official
Audit and implement a NemoClaw dependency version upgrade, including Hermes and base images.
23k GitHub stars~1.4k tokensUpdated today
DevelopmentAuto-check passed
Refactor Op
CVCUDA/CV-CUDA
Find and safely apply per-operator refactoring / redundancy-reduction opportunities in a CV-CUDA operator (near-duplicate Tensor/VarShape kernels, reinvented shared utilities, dead code).
2.7k GitHub stars~1.5k tokensUpdated 23 days ago
DevelopmentAuto-check passed
Megatron GPT to Hybrid Migration
NVIDIA/Megatron-LM
Official
Guides moving Megatron Core GPTModel checkpoints, configs, training commands and launch scripts to HybridModel, following the repository's migration document.
18k GitHub stars~1.6k tokensUpdated today
AI & LLM EngineeringAuto-check passed

Questions about Doc Reviewer

What does Doc Reviewer do?

Reviews recent code changes and checks if documentation needs updates. Doc Reviewer is an agent skill from NVlabs/alpasim. Reviews recent code changes and checks if documentation needs updates.

When should I use Doc Reviewer?

Doc Reviewer fits situations like: completing features; asked to check docs; review documentation.

How do I install Doc Reviewer in Claude Code?

Run `npx skills add NVlabs/alpasim --skill doc-reviewer -a claude-code`. Or copy the skill folder (.cursor/skills/doc-reviewer in NVlabs/alpasim) into .claude/skills/doc-reviewer in your project. Claude Code loads it when a task matches its description.

How do I install Doc Reviewer in Codex?

Run `npx skills add NVlabs/alpasim --skill doc-reviewer -a codex`. Or copy the skill folder (.cursor/skills/doc-reviewer in NVlabs/alpasim) into .agents/skills/doc-reviewer in your project. Codex loads it when a task matches its description.

Can I use Doc Reviewer in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add NVlabs/alpasim --skill doc-reviewer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/doc-reviewer, .gemini/skills/doc-reviewer, .github/skills/doc-reviewer and .opencode/skills/doc-reviewer in your project.

What does Doc Reviewer need to run?

Going by SKILL.md and its folder, Doc Reviewer needs the command-line tools its instructions call (git).

Does Doc Reviewer access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Doc Reviewer safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Doc Reviewer use?

Doc Reviewer is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Doc Reviewer use?

About 1.2k tokens (SKILL.md is roughly 5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Doc Reviewer?

Skills that share tags, products or a category with Doc Reviewer: LLM Torch Profiler Analysis (sgl-project/sglang, 37k stars), Fla Triton To Gluon (fla-org/flash-linear-attention, 5.8k stars), Megatron-LM Container and Dependency Setup (NVIDIA/Megatron-LM, 18k stars) and Nemoclaw Contributor Update Dependencies (NVIDIA/NemoClaw, 23k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Doc Reviewer?

NVlabs (a GitHub organization) maintains it in NVlabs/alpasim, which has 1,259 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on September 18, 2026.

Source: NVlabs/alpasim on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Doc Reviewer

Install Doc Reviewer

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Documentation Reviewer

Quick Start

Workflow

Step 1: Identify Changed Files

Step 2: Discover and Read All Documentation

Step 3: Analyze Impact

Step 4: Report Findings

What Triggers Documentation Updates

Example Session

Integration Points

Files

Compare with similar skills

Similar skills

LLM Torch Profiler Analysis

Fla Triton To Gluon

Megatron-LM Container and Dependency Setup

Nemoclaw Contributor Update Dependencies

Refactor Op

Megatron GPT to Hybrid Migration

More from NVlabs/alpasim

Optimize Slurm Topology

Questions about Doc Reviewer

Install Doc Reviewer

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Documentation Reviewer

Quick Start

Workflow

Step 1: Identify Changed Files

Step 2: Discover and Read All Documentation

Step 3: Analyze Impact

Step 4: Report Findings

What Triggers Documentation Updates

Example Session

Integration Points

Files

Compare with similar skills

Similar skills

LLM Torch Profiler Analysis

Fla Triton To Gluon

Megatron-LM Container and Dependency Setup

Nemoclaw Contributor Update Dependencies

Refactor Op

Megatron GPT to Hybrid Migration

More from NVlabs/alpasim

Optimize Slurm Topology

Related

Questions about Doc Reviewer