doc-sync

Doc Sync

Detect and resolve documentation drift without front-loading a full repository audit. Treat standard Claude Code Sonnet context as the baseline.

Triggers

Users may say:

• "doc sync"
• "sync docs"
• "fix doc drift"
• "reconcile docs"
• "update docs to match code"
• "update code to match docs"
• "check for documentation drift"

Parameters

direction is required:

• code-to-docs: update docs to match code
• docs-to-code: identify code gaps against docs
• full: bidirectional reconciliation with human review for conflicts

Options:

• --dry-run: report only, no file edits
• --scope <path>: limit the audit to a subtree or file group
• --incremental: start from changed files since the last sync, then current git changed files if no last-run record exists
• --parallel N: cap concurrent auditors; default 2, maximum 4

Artifact root resolution

Treat every .aiwg/... path below as a logical artifact path. Before reading or writing sync state, working evidence, or reports, run aiwg artifacts path from the active workspace and use the returned absolute directory as AIWG_ARTIFACT_ROOT. Never write these payloads to a literal project-local .aiwg/ when AIWG_ARTIFACTS_PATH or .aiwg-location redirects the corpus.

Context Budget Rules

• Start with git status --short, git diff --name-only, and git diff --cached --name-only.
• If no --scope or --incremental is supplied, derive a candidate scope from changed files and ask before expanding to the full repo.
• Use inventories (rg --files, find, git path lists) before reading file bodies.
• Dispatch auditors only for domains implicated by the scoped files.
• Each auditor returns at most 10 findings and 600 words to the parent context. Detailed evidence goes under $AIWG_ARTIFACT_ROOT/working/doc-sync/.
• Do not preload other skills into auditor agents.
• For combined doc-sync, blog, and commit requests, keep blog/release coverage as one scoped lane and return a handoff summary for commit-and-push.