You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .claude/skills/vc-update/SKILL.md
+4-44Lines changed: 4 additions & 44 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -91,41 +91,9 @@ Compare the remote manifest `version` against `currentVersion`.
91
91
-**Modifications:** Files in both lists -- compare content via `diff` between `$TMPDIR/{path}` and `{projectRoot}/{path}`.
92
92
- If identical: **unchanged**.
93
93
- If different: **modified** (note line count changes).
94
-
-**Merge files:** Files in the `merge` list that have local changes. Split into two sub-types:
95
-
-**Smart-merge** (`CLAUDE.md`, `AGENTS.md`): the agent performs an intelligent merge (see Smart Merge below). Show a preview of what will be applied vs preserved.
96
-
-**Simple-merge** (everything else in `merge`, e.g. `.claude/settings.json`): preserve local version entirely, show diff, flag for manual review.
94
+
-**Merge files:** Files in the `merge` list (e.g. `.claude/settings.json`) that have local changes. Preserve local version entirely, show diff, flag for manual review.
97
95
-**Copy-if-missing files:** Files in the `copyIfMissing` list that already exist locally. Show the diff but note they will NOT be overwritten.
98
96
99
-
### Smart Merge (CLAUDE.md and AGENTS.md)
100
-
101
-
`CLAUDE.md` and `AGENTS.md` contain both harness methodology (owned by the kit) and
102
-
project-specific content (owned by the project). When these files differ between the remote
103
-
and local versions, perform a smart merge rather than preserving or overwriting entirely.
104
-
105
-
**Apply from remote (harness methodology — kit owns these):**
106
-
- New or changed entries in the "Shared Development Protocols" file list
107
-
(lines listing files under `process/development-protocols/`)
108
-
- New or changed entries in the "Reference docs" block under development-protocols
109
-
- Changes to orchestrator role description, routing protocol, or mode detection sections
110
-
- New rows or changed rows in the skill registry table
111
-
- Changes to phase transition rules, closeout rules, or parallel fan-out checkpoints
112
-
- Any section that exists in the remote but is entirely absent locally
113
-
114
-
**Preserve from local (project-specific — project owns these):**
115
-
- The `process/context/` section bullet list and all context group entries
@@ -234,8 +194,8 @@ Version written to .vc-version: {remoteVersion}
234
194
- Always show the dry-run diff before applying. Never apply without user confirmation.
235
195
- Clean up the temp clone directory even on error or abort.
236
196
- If `.vc-version` is missing, treat as version `0.0.0` (first update, apply everything).
237
-
-`CLAUDE.md` and `AGENTS.md` are smart-merged: methodology sections updated from kit, project-specific sections (context groups, tech stack, features) preserved. Never fully overwritten, never fully skipped.
238
-
-Other files in the `merge` list (e.g. `.claude/settings.json`) are never overwritten if they exist locally. Show the diff for manual review.
197
+
-`CLAUDE.md` and `AGENTS.md` are harness-only files — overwritten freely on update. Project-specific content belongs in `process/context/all-context.md`, not in these files.
198
+
-Files in the `merge` list (e.g. `.claude/settings.json`) are never overwritten if they exist locally. Show the diff for manual review.
239
199
- Files in the `copyIfMissing` list are only installed if they don't already exist locally.
240
200
- Removals are detected by comparing the local `.vc-installed-files` snapshot against the new resolved file list.
@@ -146,18 +146,11 @@ If the user has intentional local changes to a managed file:
146
146
2. Re-apply after the update
147
147
3. Or better: move customizations to `process/context/` where they belong
148
148
149
-
### Smart-merge files (CLAUDE.md, AGENTS.md)
150
-
151
-
`CLAUDE.md` and `AGENTS.md` contain both harness methodology (kit-owned) and project-specific content (project-owned). The agent performs an intelligent merge:
152
-
153
-
-**Apply from remote:** new/changed entries in the development-protocols file list, reference docs block, orchestrator routing sections, skill registry table, phase transition rules.
154
-
-**Preserve from local:**`process/context/` bullet list and all context group entries, technology stack section, coding preferences, current features list, any section absent from the remote.
155
-
156
-
The dry-run shows a preview (`apply: +N lines | preserve: context groups, tech stack`). On apply, the merged file is written and the summary reports what was applied vs preserved.
149
+
### Merge files (.claude/settings.json)
157
150
158
-
### Simple-merge files (.claude/settings.json)
151
+
Files in the `merge` list are NEVER overwritten if they exist locally. The dry-run shows the diff so the user can manually reconcile. On fresh install (no existing file), the kit version is installed.
159
152
160
-
Files in the `merge` list (other than smart-merge files) are NEVER overwritten if they exist locally. The dry-run shows the diff so the user can manually reconcile. On fresh install (no existing file), the kit version is installed.
153
+
`CLAUDE.md` and `AGENTS.md` are harness-only files — overwritten freely on update like any other managed file. Project-specific content (context groups, tech stack, features) belongs in `process/context/all-context.md`, which vc-update never touches.
0 commit comments