docs-refresh

To update stale documentation to match your codebase, this skill orchestrates specialized subagents to compute change deltas, apply surgical edits to existing docs while preserving their original voice, and verify cross-doc consistency. It supports projects with either or both file types.

Syncing project documentation with recent code changes is handled by a 4-pass workflow that discovers deltas between docs and code, drafts prioritized edits, applies surgical modifications, and runs parallel verification checks for consistency and secret leaks.

Yes, you can refresh project docs with partial refresh modes that automatically adapt to repositories maintaining only a CLAUDE.md, only a README.md, or both. The skill exits cleanly if no target documentation exists to update.

To avoid redundant documentation refresh runs, the skill stores intermediate work in a local cache to short-circuit execution when no code changes have occurred since the last successful update, enabling fast no-change re-runs.

Yes, the documentation refresh process runs parallel verification checks specifically designed to detect secret leaks alongside cross-doc consistency validation after applying surgical edits to your CLAUDE.md and README.md files.

Updating your documentation will not alter the original structure because the skill applies surgical modifications specifically designed to preserve the original document voice and structure while aligning the content with the current codebase state.