artifact-sync

To fix drifted documentation when code changes, artifact-sync parses drift reports and recent commits to generate minimal, targeted edits for stale files. It then applies these precise updates and commits them automatically to maintain history.

Documentation drift occurs when project guides and docs become stale as code evolves. You can detect it by running a drift report, which artifact-sync parses to identify outdated entries across files like CLAUDE.md and skill docs.

Yes, you can sync CLAUDE.md and skill docs automatically with minimal edits. Artifact-sync reads changed sources and relevant commits to propose precise updates, ensuring only necessary changes are made to keep artifacts current.

The best way to update stale guides after a recent commit is to run the sync command with the fix flag. This triggers artifact-sync to read the commit range, propose minimal edits to the guides, and commit the updates with a conventional message.

Artifact-sync proposes minimal updates instead of rewriting entire files to ensure targeted synchronization. By reading diffs and applying only necessary edits, it maintains traceability and prevents unnecessary changes to documentation like CLAUDE.md and guides.

You need a drift report or a defined commit range to sync project documentation effectively. Artifact-sync relies on these inputs to identify stale entries and read changed sources, allowing it to generate and apply the correct minimal updates.