gsd-docs-update

Automate project documentation updates by running a generation process that reflects codebase changes, ensuring files stay synchronized. This skill automatically generates new documentation based on the current codebase state, saving time and reducing manual errors.

Verify documentation against the codebase without generation by using the verification mode. This allows you to check if existing documentation is synchronized with the current codebase state before deciding to commit to a full regeneration.

You need to provide scripts and reference files for operation before automating documentation synchronization. These components are required to map the codebase changes and generate or verify the associated project documentation accurately.

The best way to force a full refresh of project documentation after a codebase update is to execute the update command with the force flag. This triggers immediate regeneration of documentation to reflect the latest codebase changes.

Selective regeneration allows you to choose between regenerating all documentation or verifying it against the codebase without generation. It does not target individual files, but rather toggles between full generation and verification modes.

Documentation synchronization requires reference files to operate because they provide the necessary structural context for the scripts to map codebase changes accurately. Without these references, the automated generation cannot reliably update the documentation.