update-docs

To automatically update documentation to match code changes, this skill reads git history since a watermark commit and applies surgical edits to docs. It maps changed files to doc pages using a reference file, keeping documentation synchronized with recent code updates.

A git watermark commit for tracking documentation updates is the starting point used to compute code diffs. This skill reads the watermark to determine which repository changes occurred, mapping those modified files to the appropriate documentation pages for subsequent updates.

To map changed code files to specific documentation pages, this skill uses a code-to-doc mapping reference. It applies this mapping to files detected via git diffs, identifying exactly which pages in the docs/public directory require updates based on recent code changes.

Yes, you can use this documentation automation tool for repositories with docs in docs/public. It is specifically designed to scan this directory, read the mapping reference, and make surgical edits to affected pages, preserving the original style and structure of your documentation.

To keep documentation in sync with code without manual edits, this skill automates the synchronization process by detecting git diffs and applying surgical edits to affected pages. It reads a watermark, maps changed files to doc pages, and writes a new watermark after updating.

A limitation of automating documentation updates with git history is that this skill relies on a mapping reference file and a watermark commit. It only updates docs in the docs/public directory, making it unsuitable for unmapped code changes or repositories without this specific structure.