docs-refresh

To automate documentation updates and keep docs in sync, configure a local manifest file defining your refresh scope. The tool reads this manifest, builds targeted inventories, and writes generated content inside marker blocks without altering manual prose.

Marker blocks preserve manual prose by isolating auto-generated content within designated file sections. The refresh process writes exclusively inside these boundaries, ensuring human-written documentation outside the markers remains untouched during automated updates.

The best way to manage living documentation without auto-committing is using a manifest-driven refresh workflow. This approach updates targeted sections and surfaces conflicts or warnings without automatically committing changes to your version control system.

Yes, you can specify target sections for a codebase sync refresh. By defining the desired scope within your local manifest file, the tool restricts its inventory building and content generation to only the requested targets.

Yes, the documentation refresh tool works with both Codex and Claude manifest formats. It automatically reads project-local manifests from either the .codex/ or .claude/ directories to determine the appropriate documentation update scope.

If your manifest structure is invalid during a docs refresh, the process validates the configuration and enforces marker safety before writing. It will warn you of structural issues and surface conflicts rather than executing destructive writes.