docs-refresh

To keep documentation in sync with source files, you can automate updates to detect document drift and regenerate docs when source files change. This ensures generated API references and guides stay aligned with the latest code.

Documentation drift happens when generated docs become outdated relative to source files. You prevent drift by automating documentation-sync workflows that detect source changes and regenerate the affected markdown, rst, or mdx files.

You configure per-project documentation sync behavior by creating a .claude/skills/docs-refresh.yaml file. This configuration file tailors output formats and triggers, or you can run /docs-refresh configure to auto-detect settings.

Yes, documentation-sync automation detects multiple documentation formats including markdown, rst, and mdx. It automatically discovers documentation directories like docs, documentation, or wiki and regenerates content accordingly.

Yes, you can regenerate API references, guides, and CLAUDE.md content when source files change. The automation detects structural updates in the source and refreshes the generated documentation to maintain accuracy.

No external dependencies are required to automate documentation refresh workflows. The skill operates independently using its internal configuration file to discover directories, detect drift, and output generated and human-written docs.