claude-nomad 0.69.2 → 0.69.3

package/CHANGELOG.md

@@ -1,5 +1,21 @@
 # Changelog
 
+## [0.69.3](https://github.com/funkadelic/claude-nomad/compare/v0.69.2...v0.69.3) (2026-09-19)
+
+
+### What's new
+
+A quick follow-up to 0.69.2 for a recent change in Claude Code.
+
+* Claude Code 2.1.275 and later copy the skills enabled on your claude.ai account into `~/.claude/skills/synced/`, and can also create `skills/.trash/` and `skills/.staging/` next to it. nomad now leaves all three folders alone: `nomad push` no longer copies them into your sync repo and removes any copy an earlier push left there, `nomad pull` never touches them, and `nomad doctor` stops listing their files as out of sync.
+* To stop Claude Code syncing those skills at all, set `"syncClaudeAiSkills": false` in `~/.claude/settings.json` (on a synced machine, put it in your base or host settings file in the sync repo instead).
+
+
+### Fixed
+
+* **skills:** also skip Claude Code's skills .trash and .staging folders ([#618](https://github.com/funkadelic/claude-nomad/issues/618)) ([fbb9eb1](https://github.com/funkadelic/claude-nomad/commit/fbb9eb173842598f6aaf1be387bc73fffc1cb43f))
+* **skills:** stop syncing Claude Code's skills/synced folder ([#616](https://github.com/funkadelic/claude-nomad/issues/616)) ([59618dc](https://github.com/funkadelic/claude-nomad/commit/59618dcc25333b4bed2a7a1da73167d1be5dd660))
+
 ## [0.69.2](https://github.com/funkadelic/claude-nomad/compare/v0.69.1...v0.69.2) (2026-09-19)
 
 

package/README.md

@@ -32,13 +32,15 @@ session history survives different file paths and your secrets never ride along.
 - **One shared setup, per-machine exceptions.** Your own skills, slash commands, rules, and your
   `CLAUDE.md` live in one place and follow you everywhere. `hooks/` and `agents/` are installed
   per-host by `@opengsd/gsd-core` via npm and are not synced (syncing them caused version-skew
-  churn). Skills sync as a filtered copy: your own skills travel, `gsd-*` skills are excluded (see
-  `SHARED_LINKS` in `src/core/config.ts` and `src/sync/skills-sync.ts`). Settings merge a shared
-  base with a per-host override, so one machine can run a different model or MCP URL without forking
-  the rest. GSD-owned hook entries (scripts whose basename starts with `gsd-`) are filtered out of
-  the generated `~/.claude/settings.json` during pull and stripped from `shared/settings.base.json`
-  on the next push; GSD reinstalls the correct per-host hook set itself. A non-gsd hook you add to
-  your live settings syncs normally via `nomad capture-settings`.
+  churn). Skills sync as a filtered copy: your own skills travel, while `gsd-*` skills and Claude
+  Code's own account-skills folders (`skills/synced/`, `skills/.trash/`, `skills/.staging/`) stay
+  behind (see `SHARED_LINKS` in `src/core/config.ts` and `src/sync/skills-sync.ts`). Claude Code
+  keeps its copy of the skills enabled on your claude.ai account there. Settings merge a shared base
+  with a per-host override, so one machine can run a different model or MCP URL without forking the
+  rest. GSD-owned hook entries (scripts whose basename starts with `gsd-`) are filtered out of the
+  generated `~/.claude/settings.json` during pull and stripped from `shared/settings.base.json` on
+  the next push; GSD reinstalls the correct per-host hook set itself. A non-gsd hook you add to your
+  live settings syncs normally via `nomad capture-settings`.
 - **Every push is secret-scanned.** Only an explicit allow-list of paths ever leaves the machine,
   credentials never sync, and gitleaks scans the exact files about to be published. The push aborts
   on any hit, with an interactive menu to redact, allow, or drop the finding. Always publish through