nemoclaw-contributor-update-docs

Documentation debt is reduced by scanning recent git commits, filtering out internal changes via a skip list, mapping user-facing code modifications to existing pages, and drafting updates that follow project style and frontmatter rules.

Preparing releases with documentation updates involves scanning a specified commit range, filtering by commit types and changed files, mapping code areas to likely documentation pages, and drafting updates that enforce skip-terms to exclude experimental changes.

Yes, you can exclude experimental or internal changes by applying a project-maintained skip list via the docs/.docs-skip file, which filters excluded items and enforces skip-terms during the commit scanning and documentation drafting process.

Triage documentation debt by scanning recent git commits across CLI, blueprint, and inference areas, mapping code changes to likely documentation pages, flagging new user-visible concepts that need new pages, and grouping related commits into single doc updates.

Yes, syncing documentation to recent commits requires access to the git history, the docs directory, and the docs/.docs-skip file to filter excluded items, enforce skip-terms, and draft updates that follow project style and frontmatter rules.