update-docs-from-commits

Scan recent commits to draft or update documentation pages under docs/.

8.1k|1.2k|Updated Feb 24, 2026
One-click install
npx skills add https://github.com/NVIDIA/OpenShell --skill update-docs-from-commits-nvidia
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-docs-from-commits
Source: https://github.com/NVIDIA/OpenShell/tree/main/.agents/skills/update-docs
Command: npx skills add https://github.com/NVIDIA/OpenShell --skill update-docs-from-commits-nvidia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scan recent git history to identify changes that affect user-facing behavior and draft or update the corresponding documentation pages.

Core Features & Use Cases

  • Automatically identify commits likely to impact docs by analyzing commit messages and changed files.
  • Draft or update documentation pages under the docs/ tree to reflect code changes.
  • Use during releases to catch doc debt, align release notes, and ensure consistency between code and docs.

Quick Start

Run the update-docs-from-commits skill in your OpenShell repository to draft or update docs based on recent commits.

Frequently Asked Questions about update-docs-from-commits

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

FAQPage Schema
How do I automatically update documentation based on git commits?

The Skill analyzes commit messages and changed files to identify code changes that impact user-facing behavior. It then drafts or updates documentation pages to reflect those specific code changes.

What's the best way to catch documentation debt after a feature release?

Scanning recent git history during releases catches documentation debt by identifying commits that affect user behavior. It aligns release notes and ensures consistency between newly shipped code and existing docs.

Do I need a specific repository structure to automate docs updates from commits?

Yes, you need a repository with a defined docs tree under docs/ and a contribution or style guide. These are required to format drafted documentation pages for review properly.

How do I draft release notes from recent git history?

You can draft release notes from git history by analyzing recent commit messages and changed files. This identifies user-facing behavior modifications and drafts corresponding documentation pages for review.