quality-sync

What problem does it solve?

This Skill prevents documentation drift by automatically detecting code changes and synchronizing related documentation entries through file, component, feature, and requirement mappings so docs remain accurate and up to date.

Core Features & Use Cases

• Change detection: Uses git diffs or a full resync baseline to determine which tracked files changed and whether a sync is required.
• Impact tracing: Traces changes through file → component → feature → requirement layers via doc-index.json to build the full set of affected documentation entries.
• Safe updates: Supports dry-run previews, content-hash updates to doc-index.json, and state.json bookkeeping (last_synced, last_synced_commit) to maintain an auditable sync history.
• Use Case: After a refactor that moves or renames source files, run this Skill to automatically regenerate impacted API and architecture docs and update index timestamps without manual searching.

Quick Start

Run quality-sync with --dry-run to preview which documentation entries would be regenerated based on changes since the last synced commit.