vc-update

To safely update an agent harness, you can run a dry-run diff to preview exact file changes and create backups before applying modifications. vc-update performs a two-phase update that prompts for explicit confirmation before writing any updates.

Yes, you can preview a diff of harness updates before applying them. The skill computes changes from a remote kit manifest and enumerates exact modifications in a dry-run, prompting for user confirmation before proceeding.

You need git, Node.js, and access to a remote kit manifest to compute deterministic harness updates. These dependencies allow the process to calculate file differences, back up modified files, and write a snapshot for future diffs.

The update process handles merge-preserved files and legacy deletions during migration by computing the necessary changes against a snapshot. It uses a two-phase approach to ensure these migrations are applied safely after user confirmation.

You should run an agent harness update when applying new harness versions, updating after bootstrap, or performing periodic maintenance across diverse project stacks. This ensures your agent environment stays current with remote repository improvements.

Yes, vc-update works across diverse project stacks for periodic maintenance and version updates. It pulls the latest improvements from a remote kit repository and safely applies them using a deterministic, two-phase update process.