Verified:GitHub

update

Detect and apply incremental Anti-Vibe Coding plugin updates via checksums.

Updated Mar 8, 2026

Search Tags:#plugin update #backup safety #anti-vibe-coding #manifest sync #incremental merge #checksum validation #CLAUDE.md governance

Ready to run

npx skills add https://github.com/luyzkk/Anti-Vibe-Coding --skill update-luyzkk

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: update
Source: https://github.com/luyzkk/Anti-Vibe-Coding/tree/main/skills/update
Command: npx skills add https://github.com/luyzkk/Anti-Vibe-Coding --skill update-luyzkk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents Anti-Vibe Coding installations from silently drifting out of date by detecting outdated or missing files and applying controlled incremental updates inside an existing project.

Core Features & Use Cases

Update detection via local manifest: Compares the plugin’s plugin-manifest.json against the project’s .claude/.anti-vibe-manifest.json using versions and installed checksums to identify new, outdated, and user-modified files.
Interactive, file-safe rollout: Presents organized update options (update all, choose per file, inspect diffs, or cancel) and creates backups before changes.
Guardrails for high-risk files (CLAUDE.md): Applies CA-07 by requiring explicit section-by-section confirmation for any added/changed CLAUDE.md sections, otherwise skipping them.
Merge strategies by file type: Supports replace, merge (including special handling for CLAUDE.md and rules/*.md), and never (ignore), then refreshes the local manifest checksums and version.

Quick Start

Run the update process in your current project directory by asking the AI to: /anti-vibe-coding:update

Frequently Asked Questions about update

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

FAQPage Schema

How do I safely update plugin files in an existing project without losing my local changes?▼

To safely update plugin files, the update process compares local checksums against plugin manifests, creates backups before applying changes, and uses intelligent merge or replace strategies to preserve local modifications while syncing incremental updates.

How does incremental merge handle version control for CLAUDE.md governance files?▼

Incremental merge for CLAUDE.md governance files enforces CA-07 confirmation rules, requiring explicit section-by-section approval for any added or changed content, and automatically skips sections that are not explicitly confirmed by the user.

How do I detect outdated or missing files from a plugin installation in my project?▼

File update detection works by comparing the plugin's plugin-manifest.json against the project's .claude/.anti-vibe-manifest.json using installed checksums and version numbers to identify new, outdated, and user-modified files.

Can I preview file changes and select which updates to apply during a plugin sync?▼

Yes, the plugin sync process supports interactive selection, allowing you to inspect per-file diffs, update all files, choose specific files to update, or cancel the operation entirely before any modifications are made to your project.

What are the merge strategy options when syncing manifest updates to my project?▼

The sync supports three merge strategies: replace overwrites the entire file, merge combines content with special handling for CLAUDE.md and rules/*.md files, and never ignores the file entirely. The local manifest is refreshed with new checksums after applying updates.

Why does my local manifest checksum not match the installed plugin version after an update?▼

Manifest checksum mismatches occur when local files have been modified or when incremental updates have not been applied. Running the update process validates checksums against the plugin manifest, applies necessary changes, and refreshes the local manifest to match the installed version.