Problem
When hermes update hits:
→ Syncing bundled skills...
it only reports aggregate counts. If a bundled skill was skipped because the local copy is user-modified, the user gets told it was "kept" but not which skill it was.
That is a real problem: once the update is done, there is no way to know which skills were dirtied locally, so the user cannot later compare the upstream/origin version against their modified version and decide whether to keep their changes or take the remote update.
Ask
Print the names of the user-modified skills that were kept unmodified during bundled skill sync.
Example:
→ Syncing bundled skills...
~ 3 user-modified (kept): hermes-agent, debugging-hermes-tui-commands, system-health
If the list is long, truncate it and show the remainder count.
Why this matters
The current output hides the exact skills that need triage. Count-only output is useless once the update finishes because the user loses the inventory of locally dirtied skills.
Related
This issue is the narrower UX gap: show the exact kept local skill names during the bundled sync step so the user can act on them later.
Problem
When
hermes updatehits:it only reports aggregate counts. If a bundled skill was skipped because the local copy is user-modified, the user gets told it was "kept" but not which skill it was.
That is a real problem: once the update is done, there is no way to know which skills were dirtied locally, so the user cannot later compare the upstream/origin version against their modified version and decide whether to keep their changes or take the remote update.
Ask
Print the names of the user-modified skills that were kept unmodified during bundled skill sync.
Example:
If the list is long, truncate it and show the remainder count.
Why this matters
The current output hides the exact skills that need triage. Count-only output is useless once the update finishes because the user loses the inventory of locally dirtied skills.
Related
This issue is the narrower UX gap: show the exact kept local skill names during the bundled sync step so the user can act on them later.