sync

Template sync detects drift between your seeded project's files and repository templates, allowing you to interactively pull updates, push local changes, or skip divergences. It compares skills, Dockerfiles, and scripts to prevent breakage from mismatched configurations.

Dockerfile drift is detected using deterministic file comparison logic that treats resolved placeholders like {{TOOLCHAIN_SETUP}} as expected. The sync process compares your local Dockerfile against auto-engineer repository templates to identify divergences for interactive resolution.

Yes, you can push local script changes back to templates, but safety guards warn before pushing anything that might include resolved project-specific placeholder values. Explicit confirmation is required to prevent unsafe template pushes that could corrupt template definitions.

Yes, template sync requires YAML-defined discovery metadata to perform configuration reconciliation. This metadata enables the tool to discover and compare skills, Dockerfiles, and scripts between your target project and auto-engineer templates for two-way diff detection.

Configuration drift in .claude/ files is resolved through interactive per-file choices. For each divergence found between your project and templates, you can pull template updates into the target, push local changes back, view a diff, or skip the file entirely.

Resolved Dockerfile placeholders like {{TOOLCHAIN_SETUP}} are treated as expected values during comparison. The sync logic recognizes these resolved project-specific placeholders to avoid false drift detection when comparing your local Dockerfile against template definitions.