sync-docs

To automate documentation updates, scan recent git commits to identify changed actions and reusable workflows, then refresh only the touched targets and synchronize the catalog.

The best way to keep repository documentation current is to scan recent git commits and automatically propagate changes across all affected action and workflow documentation sections.

Automated documentation sync reads SKILL.md-based targets in the repository to determine which workflow and action documentation sections need to be generated or updated after recent commits.

Yes, target-aware updates detect changes in actions and reusable workflows and refresh only the touched targets, ensuring documentation updates are scoped to recently modified code.

Yes, synchronizing documentation and catalogs requires access to git history to scan the last N commits and identify which actions and reusable workflows have been changed.

You should avoid automated documentation synchronization when your repository does not use SKILL.md-based targets or when you lack the required git history access needed to scan recent commits.