gsd-docs-update

To update project documentation, run a workflow that inspects the codebase directly and regenerates markdown based on actual source code evidence. This ensures your docs reflect current APIs, paths, and signatures without manual checks or hallucinated details.

You can verify existing markdown documentation against the source code by triggering a verification-only run. This checks your docs for mismatched APIs, incorrect paths, and outdated descriptions without regenerating the files, catching stale signatures effectively.

Yes, you can refresh documentation across multiple packages in a monorepo. The workflow supports monorepo-aware dispatch, allowing it to handle complex repositories and update up to nine project docs simultaneously while preserving existing structures.

Automated documentation generation avoids hallucinated file paths by requiring direct codebase inspection and applying workflow gating with preservation checks. It generates content strictly from source code evidence, verifying outputs without relying on guessed locations.

You can regenerate or verify up to nine project docs in a single workflow run. This limit applies to documentation creation and refreshing tasks across evolving projects and monorepos to ensure thorough codebase inspection.