vc-update

Syncs agent harness files from a remote kit repository with dry-run diff and confirmation.

2|Updated Sep 15, 2025
One-click install
npx skills add https://github.com/marsley01/Marsley-Portfolio-Web --skill vc-update-marsley01
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vc-update
Source: https://github.com/marsley01/Marsley-Portfolio-Web/tree/main/.agents/skills/vc-update
Command: npx skills add https://github.com/marsley01/Marsley-Portfolio-Web --skill vc-update-marsley01

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Keeping a project's AI agent harness (agents, skills, hooks, settings) in sync with an upstream kit repository is error-prone: manual copying risks overwriting user customizations, missing stale files, or losing legacy content. This Skill automates the update with a safe dry-run, explicit confirmation, backups, and migration of legacy layouts. ## Core Features & Use Cases - Dry-run diff before applying: Clones the remote kit, resolves its manifest, computes add/modify/delete/preserve sets via compute-sync-plan.mjs, and prints a summary that requires explicit user confirmation before any change. - Safe apply with backups and snapshotting: Backs up modified and deleted files to .vibecode-backup/ (with rotation), applies the plan mechanically, fixes symlinks, writes .vc-installed-files and .vc-version, and guards .gitignore. - Legacy layout migration: Detects old-layout process/ artifacts (flat plan files, sibling reports//references/ dirs), migrates safe cases into task folders, and logs orphaned dirs for manual review. - Use Case: After a new harness release is announced, run the update to see exactly which of the 90+ managed files will change, preserve your merge-protected .claude/settings.json, and apply the upgrade with a recoverable backup. ## Quick Start Ask the agent to check for and apply the latest harness updates from the kit repository, reviewing the dry-run diff before confirming.

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 the vc-update skill, which clones the remote kit, resolves its manifest, and prints a dry-run diff of files to add, modify, or delete. Type 'apply' to confirm; it backs up changed files to .vibecode-backup/ before applying.

Will the update overwrite my custom settings.json changes?

No. Files in the manifest's merge list, such as .claude/settings.json, are never overwritten when they exist locally. The dry-run shows the diff so you can manually reconcile new hooks or settings.

Can I test the update against a local kit copy instead of GitHub?

Yes. Set the VC_KIT_SOURCE environment variable to a local path or alternate URL, and it is used verbatim as the git clone source. This enables offline testing, forks, and pinned versions.

What happens if the update deletes files I still need?

Every file scheduled for modification or deletion is first backed up to .vibecode-backup/, and prior backups are rotated to timestamped directories. Deletions also pass a namespace guard, and suspicious paths are preserved with warnings.

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 process artifacts exist, it migrates them into task folders without changing the version.

What are the limitations when updating from very old kit versions?

Installs predating legacyDeletions support in SKILL.md cannot migrate cleanly through vc-update. For those very old installs, use the kit's install.sh for a clean reinstall instead.