nemoclaw-contributor-update-docs

Scan recent git commits and draft NemoClaw documentation updates.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically generate up-to-date documentation from code changes to ensure documentation matches the current software behavior.

Core Features & Use Cases

  • Scan recent git commits for user-facing changes
  • Draft or update docs in the docs/ pages
  • Assist releases by catching documentation gaps

Quick Start

Run the contributor update-docs skill in the NemoClaw repository to generate fresh documentation from the latest commits.

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 automatically generate documentation from git commits?

You can automatically draft documentation from git commits by scanning recent changes that affect user-facing behavior, outputting structured updates with YAML-ready metadata and frontmatter.

What is the best way to catch documentation gaps before a software release?

Catching documentation gaps before a release involves scanning recent code commits to identify user-facing changes and automatically drafting corresponding updates for the affected docs pages.

How do I keep documentation synchronized with code changes during feature batches?

Documentation synchronization during feature batches works by analyzing recent git commits to detect behavior changes, then drafting updates for onboarding flows, reference stacks, and policy notes.

Does the docs update process enforce structured frontmatter and metadata?

Yes, the docs update process enforces structured frontmatter, links to docs directories, and outputs YAML-ready metadata including dependencies, components, and safety checks for consistent formatting.

Can I use this documentation drafting approach for any repository?

This documentation drafting approach targets the NemoClaw repository specifically, scanning commits that affect user-facing behavior across onboarding flows, reference stacks, and policy notes.

What types of documentation pages can be updated by scanning recent commits?

Scanning recent commits can draft or update documentation pages covering onboarding flow, reference stacks, and policy notes based on detected user-facing behavior changes.