update-docs

Detect source code changes and update corresponding documentation pages.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Updates and aligns documentation pages with the latest source code changes by automatically detecting diffs and applying targeted edits.

Core Features & Use Cases

  • Detects changed source files via git diff and consults the mapping in SOURCE_DOC_MAPPING.md to identify affected docs.
  • Creates new documentation pages when a source file has no existing page, and updates server/docs.json and navigation entries accordingly.
  • Preserves formatting and style across sections (Configuration, InputParams, Event Handlers) while keeping docs accurate and up-to-date.

Quick Start

Run the update-docs skill on your main branch to generate and apply documentation updates from code changes.

Frequently Asked Questions about update-docs

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

FAQPage Schema
How do I keep documentation in sync with code changes automatically?

To keep documentation in sync with code changes, this skill analyzes git diffs, consults the SOURCE_DOC_MAPPING.md file to identify affected docs, and applies targeted edits to maintain alignment between source code and documentation pages.

What is the best way to update docs.json and navigation structures when source code evolves?

Updating docs.json and navigation structures is handled automatically by detecting changed source files and synchronizing the documentation navigation entries to reflect new or modified pages when source code evolves.

How does mapping between source files and documentation pages work?

The mapping between source files and documentation pages works by reading the SOURCE_DOC_MAPPING.md file, which links code files to their corresponding docs, enabling targeted updates whenever a code diff is detected.

Can I create new documentation pages when a source file has no existing page?

Yes, you can create new documentation pages when a source file has no existing page. The skill automatically generates the new page and updates server/docs.json and navigation entries to include it.

Does updating documentation automatically preserve formatting across Configuration and InputParams sections?

Yes, updating documentation automatically preserves formatting and style across sections like Configuration, InputParams, and Event Handlers while keeping the docs accurate and up-to-date with the latest code changes.

What do I need to set up before automating documentation alignment with code diffs?

To automate documentation alignment with code diffs, you need a main branch with git history and a SOURCE_DOC_MAPPING.md file defining the relationships between your source files and documentation pages.