nemoclaw-contributor-update-docs

Scan git history and update NemoClaw documentation for user-facing commits.

Updated May 23, 2026
One-click install
npx skills add https://github.com/yo-steven/skills-exploration-20260522 --skill nemoclaw-contributor-update-docs-yo-steven
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nemoclaw-contributor-update-docs
Source: https://github.com/yo-steven/skills-exploration-20260522/tree/main/skills/NemoClaw/nemoclaw-contributor-update-docs
Command: npx skills add https://github.com/yo-steven/skills-exploration-20260522 --skill nemoclaw-contributor-update-docs-yo-steven

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents documentation from drifting behind recent NemoClaw code changes, so users do not miss new flags, behaviors, or defaults during daily work or release prep.

Core Features & Use Cases

  • Commit-to-doc mapping: Scans recent git history for commits that affect user-facing behavior, then drafts updates for the most relevant documentation pages.
  • Skip controls and safety gates: Honors docs/.docs-skip to avoid documenting excluded features or forbidden terms, and filters out agent documentation when the agent is not in the tested support matrix.
  • Release-prep refresh workflow: When invoked for release prep, updates docs version metadata and refreshes generated NemoClaw user skills for the target release.

Quick Start

Use the nemoclaw-contributor-update-docs skill to catch up your NemoClaw documentation after a batch of merged changes by scanning commits since v0.1.0, drafting the affected docs pages, and running the docs build to verify the updates.

Frequently Asked Questions about nemoclaw-contributor-update-docs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I sync documentation with recent git commits before a release?

The Skill syncs documentation to recent code changes by scanning git history for commits affecting user-facing behavior, mapping them to relevant doc targets, drafting updates, and verifying the result by building the docs.

What is docs drift and how do I prevent it after merging features?

Docs drift happens when user documentation falls behind code changes. You prevent it by scanning git history for user-facing commits, drafting updates for affected documentation pages, and running a docs build to verify the synchronization.

Can I exclude specific features or terms from documentation updates?

Yes, you can exclude specific features or terms by configuring a docs/.docs-skip list. The Skill honors this skip list to avoid documenting excluded features or forbidden terms and filters out unsupported agent documentation.

How do I map git commits to the correct MDX documentation pages?

You map git commits to MDX documentation pages by scanning recent git history for user-facing behavior changes and automatically drafting updates for the most relevant documentation targets affected by those commits.

Does the documentation refresh workflow update version metadata for release prep?

Yes, when invoked for release prep, the Skill updates docs version metadata and optionally refreshes generated NemoClaw user skills for the target release to ensure documentation matches the release version.

Why should I use a skip list when updating documentation from code changes?

You use a skip list to enforce safety gates when updating documentation from code changes, preventing the documentation of excluded features, forbidden terms, and agents outside the tested support matrix.