vc-update

Pull and apply agent harness updates from a remote kit repository with dry-run confirmation.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/HyuseCS/project-c --skill vc-update-hyusecs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vc-update
Source: https://github.com/HyuseCS/project-c/tree/main/.claude/skills/vc-update
Command: npx skills add https://github.com/HyuseCS/project-c --skill vc-update-hyusecs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Keeping a project's agent harness files in sync with an upstream kit repository is error-prone: manual copying risks overwriting user customizations, missing stale file removals, or losing legacy content. This Skill automates the update with a safe dry-run diff, explicit confirmation, backups, and legacy layout migration. ## Core Features & Use Cases - Dry-run diff with confirmation: Clones the remote kit, resolves its manifest, computes add/modify/delete/preserve plans via compute-sync-plan.mjs, and shows a summary before applying anything. - Safe apply with backups: Backs up modified and deleted files to .vibecode-backup/ (with rotation), applies the sync plan, fixes symlinks, and writes .vc-version and .vc-installed-files snapshots. - Legacy layout migration: Moves old-layout process/ plan, report, and reference artifacts into task folders when a destination can be safely inferred, and reports ambiguous cases for manual review. - Use Case: After being told a new harness version is available, run the update to see exactly which agent, hook, and skill files will change, confirm, and let the tool apply the update while preserving merge-protected files like .claude/settings.json. ## Quick Start Ask the assistant to run vc-update to check for and apply the latest agent harness updates from the remote kit repository.

Frequently Asked Questions about vc-update

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update my agent harness to the latest kit version?

Run vc-update, which clones the remote kit repository, resolves its manifest, and shows a dry-run diff of files to add, modify, or delete. Type 'apply' to confirm and the update is applied with backups written to .vibecode-backup/.

How do I test a harness update from a local kit copy?

Set the VC_KIT_SOURCE environment variable to a local path or alternate URL before running the update. The value is used verbatim as the git clone source, enabling offline testing and forks.

Will vc-update overwrite my customized .claude/settings.json?

No. Files in the manifest's merge list, including .claude/settings.json, are never overwritten when they exist locally. The dry-run shows the diff so you can reconcile changes manually, and a post-update notice lists hooks you may need to add.

What happens if the update deletes files I still need?

Every file scheduled for modification or deletion is backed up to .vibecode-backup/ before applying, and prior backups are rotated to timestamped directories. Deletions also pass a namespace guard, and suspicious large-delete batches trigger a prominent warning.

Why does vc-update say already up to date but still run a migration?

Version equality makes the file sync a no-op, but the legacy layout migration is not version-gated. If old-layout plan, report, or reference artifacts exist under process/, they are scanned and safely migrated into task folders even when versions match.

What are the limitations of vc-update on Windows?

The backup step in Part A assumes a POSIX shell and uses /dev/stdin, so it must be skipped or adapted on Windows. Symlink creation may also fall back to real directories, which the post-update check re-syncs from .claude/skills/.