Skip to content

chore(skill): remove skill update + drop sync-noise output#387

Merged
christso merged 1 commit into
mainfrom
chore/remove-skill-update-cleanup-sync-noise
May 12, 2026
Merged

chore(skill): remove skill update + drop sync-noise output#387
christso merged 1 commit into
mainfrom
chore/remove-skill-update-cleanup-sync-noise

Conversation

@christso
Copy link
Copy Markdown
Contributor

Summary

Two cleanups against the recently-merged skill * group.

1. Remove allagents skill update

The command was metadata-only — it rewrote sources[...].skills[*].contentHash / updatedAt and stamped pinnedRef, but it never copied any files into the client directories. allagents update already does the real refresh (fetch from remote + copy via syncWorkspace), so the per-skill command was a redundant footgun: a user running it after upstream changed would see "✓ updated" while their installed skills stayed at the old version.

Removed:

  • updateCmd definition + SkillUpdateRow type in src/cli/commands/plugin-skills.ts
  • skillsUpdateMeta in src/cli/metadata/plugin-skills.ts
  • The update: entry in skillsCmd.cmds
  • The wiring in src/cli/agent-help.ts (allCommands array + import)
  • The matching test fixture in tests/unit/cli/agent-help.test.ts (count 18 → 17, 'skill update' removed from the expected-names list)
  • The now-unused loadSyncState import

The supporting helpers (computeSkillFolderHash, upsertSyncStateSource, upsertSyncStateSkill, resolveSkillFolder) stay — they're still used by recordContentProvenance on the skill add path so drift detection keeps working.

2. Drop "Syncing workspace… / Sync complete." noise in skill add / skill remove

Six call sites printed

✓ Enabled skill: brainstorming (superpowers)

Syncing workspace...

Sync complete.

The first and last lines were redundant — ✓ Enabled/Disabled skill: … already confirms the action, and the sync output (per-client artifact counts) follows when there's something to report. Removed all six.

Test plan

  • bun run build
  • bun run typecheck
  • bun test — 1209 pass / 0 fail
  • No remaining Syncing workspace or Sync complete strings in src/cli/commands/plugin-skills.ts
  • No remaining references to updateCmd, SkillUpdateRow, skillsUpdateMeta, or skill update anywhere in src/ or tests/

…d/remove

`skill update` was metadata-only — it rewrote sync-state hashes but didn't
copy any new files. `allagents update` already does the real refresh (fetches
from remote + copies into the client dirs), so the per-skill command was a
redundant footgun. Drops it entirely:
- src/cli/commands/plugin-skills.ts: remove `updateCmd`, the `SkillUpdateRow`
  type, the unused `loadSyncState` import, and the `update:` entry in
  `skillsCmd.cmds`. The helpers `resolveSkillFolder`,
  `computeSkillFolderHash`, `upsertSyncStateSource`, and
  `upsertSyncStateSkill` stay — they're still used by `recordContentProvenance`
  on the `skill add` path.
- src/cli/metadata/plugin-skills.ts: delete `skillsUpdateMeta`.
- src/cli/agent-help.ts: drop the import and the entry in `allCommands`.
- tests/unit/cli/agent-help.test.ts: drop the import, the entry, the count
  goes 18 → 17, and 'skill update' is removed from the expected-names list.

Also drops the redundant "Syncing workspace... / Sync complete." pair from
the `skill add`/`skill remove` handlers (six call sites). The
"✓ Enabled/Disabled skill: ..." line already confirms the action and the
sync output (file counts per client) follows when there's something to
report; the two extra status lines are pure noise between them.
@cloudflare-workers-and-pages
Copy link
Copy Markdown

Deploying allagents with  Cloudflare Pages  Cloudflare Pages

Latest commit: 744ee82
Status: ✅  Deploy successful!
Preview URL: https://10e63e97.allagents.pages.dev
Branch Preview URL: https://chore-remove-skill-update-cl.allagents.pages.dev

View logs

@christso christso merged commit 225534f into main May 12, 2026
1 check passed
@christso christso deleted the chore/remove-skill-update-cleanup-sync-noise branch May 12, 2026 21:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant