nemoclaw-contributor-update-docs

Scans git commits for user-facing changes and drafts corresponding MDX documentation and changelog updates.

Updated Aug 1, 2026
One-click install
npx skills add https://github.com/Army161/NemoClaw --skill nemoclaw-contributor-update-docs-army161
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nemoclaw-contributor-update-docs
Source: https://github.com/Army161/NemoClaw/tree/main/.agents/skills/nemoclaw-contributor-update-docs
Command: npx skills add https://github.com/Army161/NemoClaw --skill nemoclaw-contributor-update-docs-army161

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Documentation often falls behind code changes, leaving users with stale or missing guidance before releases. This Skill scans recent git history for user-facing commits, maps them to the correct doc pages, drafts style-compliant updates, and produces the canonical dated changelog entry needed for pre-tag release prep. ## Core Features & Use Cases - Commit-to-Doc Mapping: Filters git history by commit type, changed files, and a configurable skip list (docs/.docs-skip), then maps each relevant commit to the doc page that owns the behavior. - Style-Compliant Drafting: Applies NemoClaw documentation conventions including active voice, $$nemoclaw CLI placeholders, correct NVIDIA/NemoClaw/OpenShell capitalization, and MDX SPDX headers. - Release Prep Workflow: Creates or updates docs/changelog/YYYY-MM-DD.mdx with an exact ## vX.Y.Z heading, applies the correct release label, and opens a labeled docs PR. - Use Case: Before cutting release v0.0.63, run the skill to scan <previous-tag>..origin/main, update affected MDX pages, generate the dated changelog entry, and open a PR labeled area: docs and v0.0.63. ## Quick Start Ask the agent to catch up the docs for everything merged since the last release tag, for example by saying update docs for all commits since v0.1.0.

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 update documentation from recent git commits?

Run the skill with a commit range such as a tag or commit count. It scans git log for feat, fix, refactor, and perf commits touching user-facing code, maps each to the owning doc page, and drafts style-compliant MDX updates.

How do I create a release changelog entry before cutting a tag?

Invoke the skill for release prep with a target version. It derives the previous release tag, scans commits up to origin/main, and creates docs/changelog/YYYY-MM-DD.mdx with an exact ## vX.Y.Z heading, summary, and linked bullets.

Can I exclude experimental features from generated documentation?

Yes. Add feature names or terms to docs/.docs-skip under skip-features or skip-terms. Matching commits are excluded from drafting, and any drafted sentence containing a skip-term is removed as a hard gate.

What happens if the release label does not exist when opening the docs PR?

The skill stops before PR creation and reports the missing label. It does not substitute another label or open an unlabeled release-prep PR, so you must create the vX.Y.Z label first.

Does the skill verify documentation changes before opening a PR?

Yes. It runs npx vitest run test/changelog-docs.test.ts and npm run docs to check for build errors, broken cross-references, and navigation mismatches before committing and opening the pull request.