📦 Skylv File History Tracker — Skylv 文件历史记录跟踪器

skylv-file-versioning Git——，，，。 Skill Metadata Slug: skylv-file-versioning Version: 1.0.0 Description: Git——。 Category: file Trigger Keywords: version control, file history, diff, restore, snapshot, rollback, track changes Capabilities 1. Snapshot (Version Capture) node version_engine.js snap [message] # Example: node version_engine.js snap config.json "update API key" .fvsnap/ (next to the file) + Binary-safe (images, PDFs, JSON, ) 2. History node version_engine.js history # Example: node version_engine.js history config.json version, date, message, hash (first 8 chars) --limit N 3. Diff (Between Versions) node version_engine.js diff [v1] [v2] # Example: node version_engine.js diff config.json 2 1 Side-by-side unified diff Line numbers Color-coded: additions (green), deletions (red) Binary files: hash HEAD~N 4. Tag node version_engine.js tag version tag # Example: node version_engine.js tag config.json 3 v1.0.0 .fvsnap/tags.json node version_engine.js tags 5. Restore node version_engine.js restore [version] # Example: node version_engine.js restore config.json v1.0.0 .fvsnap/ 6. Compare (Any Two Files) node version_engine.js compare file2 # Example: node version_engine.js compare old.json new.json Line-by-line diff 7. Auto-Snapshot (Watch Mode) node version_engine.js watch file-or-dir [--interval ms] # Example: node version_engine.js watch config.json --interval 5000 Ctrl+C Architecture Storage Format project/ ├── config.json └── .fvsnap/ ├── config.json.json ├── config.json.log └── tags.json Snapshot File Format { "version": 3, "hash": "a3f8b2c1...", "message": "update API key", "timestamp": "2026-04-17T10:30:00.000Z", "size": 1247, "content": "..." } Diff Algorithm Text files: LCS (Longest Common Subsequence) based diff Binary files: hash comparison only Max display: 200 context lines per chunk Real Market Data (2026-04-11 ) Metric Value Incumbent visual-file-sorter (score: 1.022) Incumbent weakness Our target Improvement potential Significant — real version control vs. file sorting Why visual-file-sorter Is Not Real Competition visual-file-sorter — file organization, not file versioning. Real version control needs: Content hashing (detect changes) Diff viewing (see what changed) Restore capability (go back) Tagging (mark milestones) This skill delivers all four. visual-file-sorter delivers none. Usage Examples Daily Workflow # Before editing a config file, snapshot it node version_engine.js snap .env "before changing DB password" # Make changes... # See what changed node version_engine.js diff .env HEAD~1 HEAD # Tag the working version node version_engine.js tag .env HEAD v1.2.0 # Realized something broke? Restore node version_engine.js restore .env v1.2.0 OpenClaw Integration Ask OpenClaw: "snapshot my config files" or "show diff between version 3 and 5 of settings.json" Compare: file-versioning vs visual-file-sorter Feature file-versioning visual-file-sorter Content hashing SHA-256 Snapshot history Full history Diff viewing LCS-based Tag support Named tags Restore to previous Any version Binary file support Auto-watch mode Pure Node.js No git required Built by an AI agent that actually version-controls its own config files. Install openclaw skills install skylv-file-versioning