Update documentation pages by applying surgical edits based on code changes since the last watermark.
npx skills add https://github.com/fabro-sh/fabro --skill update-docs-fabro-sh
Please help me install this Agent Skill. Skill: update-docs Source: https://github.com/fabro-sh/fabro/tree/main/.claude/skills/docs Command: npx skills add https://github.com/fabro-sh/fabro --skill update-docs-fabro-sh
Documentation often falls out of date when code changes are made, causing confusion and wasted time. This Skill automatically detects code changes since the last run using a watermark, and updates documentation pages to stay in sync with the codebase.
Run the update-docs workflow to refresh docs/public based on code changes since the watermark.
High-intent search queries and answers about installing and using this skill.
You can automatically update documentation by reading a git watermark to collect code changes since the last run, cross-referencing a code-to-doc mapping, and applying surgical edits to affected pages to keep docs in sync.
A watermark in git documentation synchronization is a recorded HEAD hash used to track the last processed state, enabling the collection of subsequent code changes to identify and update only the affected documentation pages.
You map code changes to specific documentation pages by using a code-to-doc mapping file that cross-references modified source files with their corresponding docs, allowing targeted surgical edits on only the affected pages.
Yes, update-docs works without external dependencies, relying solely on its internal references component to read git watermarks, gather code changes, apply surgical edits to docs, and write the latest HEAD hash to enforce the patch cycle.
The best way to keep docs in lockstep with code changes is to run an automated workflow that gathers commits since a watermark, cross-references a code-to-doc mapping, applies surgical edits to affected pages, and updates the watermark.
You should not use automated documentation updates when your project lacks a defined code-to-doc mapping or a git watermark, as the system requires these to identify affected pages and perform surgical edits accurately.
cipherstashSynchronize project documentation with code changes using a two-phase workflow.
frostantConverts git commit history into categorized, ready-to-publish markdown release notes.
robertbr123Automate code review with security scans, quality checks, and automated fixes.
dt418Build documentation platforms with versioned docs, search, navigation, code highlighting, and API reference generation.
