skills.rest
cryborg1211
cryborg1211COMMUNITY
Explore all skills by this author →
GitHub

vc:update

Compare local and remote harness versions, preview file diffs, and apply updates after approval.

Updated May 10, 2026
Search Tags:#automation#git#diff#update#version#harness
One-click install
npx skills add https://github.com/cryborg1211/quant_trading_telegram_bot --skill vc-update
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: vc:update
Source: https://github.com/cryborg1211/quant_trading_telegram_bot/tree/main/.agents/skills/vc-update
Command: npx skills add https://github.com/cryborg1211/quant_trading_telegram_bot --skill vc-update

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates safe updates of the agent harness by performing a dry-run diff before applying changes to the local project.

Core Features & Use Cases

  • Dry-run diff: previews additions, removals, and modifications to the harness files.
  • Version-aware updates: compares local version with remote manifest and proceeds only when remote is newer.
  • Confirmation gate: requires user approval before applying changes, with a clear dry-run summary.
  • Safe handling of special files: preserves local changes for merge and copy-if-missing files, and reports potential conflicts.

Quick Start

Use vc-update to preview the changes and then type apply to perform the update.

Frequently Asked Questions about vc:update

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

FAQPage Schema
How do I safely update a git harness without losing local file changes?▼

A dry-run diff previews additions, removals, and modifications before applying harness updates. This process preserves local modifications using merge-copy semantics and copy-if-missing rules, ensuring local file changes are not lost during the version upgrade.

What is a dry-run diff for agent harness version updates?▼

A dry-run diff is a preview mechanism that compares local harness files against a remote manifest. It resolves file-level differences, checks symlinks, and presents a summary of pending changes, requiring user confirmation before applying any modifications.

How do I automate agent harness updates during regular maintenance?▼

Automate harness updates by running a version comparison against the remote manifest to verify a newer version exists. The automation then executes a dry-run diff, waits for user approval at the confirmation gate, and applies the file-level changes to complete the maintenance safely.

Does the harness update process detect symlink conflicts?▼

Yes, the harness update process detects symlink conflicts. During the dry-run diff phase, the system performs symlink checks alongside file-level diffs and reports potential conflicts, ensuring special files are handled safely before any changes are applied to the local project.

Can I preview harness file removals before applying a version upgrade?▼

Yes, you can preview harness file removals before applying a version upgrade. The dry-run diff explicitly previews additions, removals, and modifications, giving you a clear summary to review before you type apply to authorize the actual update process.

Related Skills

Explore More Software Engineering Skills→
lovecrushfamilylovecrushfamily
1

vc-update

Compare local harness versions with a remote kit repository and apply updates after dry-run confirmation.

Community
Advanced
TETRA2000TETRA2000

import-project

Import project archives into workspace directories with configurable conflict strategies.

Community
Intermediate
erguotou520erguotou520

update-nanoclaw

Synchronize a NanoClaw fork with upstream changes while preserving local modifications.

Community
Advanced
tutran27tutran27

vc-update

Automate agent harness updates from a remote repository with dry-run diff summaries.

Community
Advanced