rawgentic:update-docs

To keep documentation accurate and aligned with code, you can use an automated workflow that audits factual claims against your codebase, drafts updates, verifies accuracy, and creates pull requests with conventional commits.

Automating API reference documentation updates involves a guided workflow that validates scope, drafts content, verifies factual accuracy against actual code, and submits a conventional commit pull request for user review.

Code verification for documentation updates works by enforcing an accuracy-first principle where all factual claims in the drafted docs are systematically checked against the actual codebase before user review.

Yes, you can use conventional commits for documentation pull requests by orchestrating a workflow that drafts, verifies, and submits doc updates with properly formatted commit messages.

Automated documentation audits require scope validation and user review, meaning the workflow guides drafting and accuracy verification against code but still depends on human approval before final pull request creation.

Yes, you need to manually review generated documentation because the workflow includes a mandatory user review stage after code accuracy verification and before the final pull request is created.