update-docs

You can update package documentation to reflect code changes by detecting modified files across packages, mapping them to existing docs, and spawning parallel sub-agents to refresh each affected package's documentation automatically.

The best way to keep documentation in sync is to detect changed files since the last git push, filter for existing docs in affected packages, and regenerate those documentation surfaces in parallel.

This approach works with existing docs by filtering for them first, then updating or regenerating the documentation surfaces for affected packages and merging the new content with existing material.

You should use an automated documentation update workflow during releases or code reviews to maintain a single source of truth, ensuring all package docs accurately reflect code changes since the last push.

Parallel sub-agent processing works by identifying all affected packages with changed files, then spawning concurrent sub-agents to refresh each package's documentation simultaneously and summarize the update results.