Hivemind turns agent traces into skills and shares with your team

Closes #114.

Summary

Hard switch from skilify to skillify across the tree. The CLI subcommand and module were named skilify but the natural derivation from skill is skillify. No deprecation alias — hivemind skilify ... now returns Unknown command: skilify.

Scope

• src/skilify/ -> src/skillify/ (incl. skilify-worker.ts, spawn-skilify-worker.ts)
• src/commands/skilify.ts -> skillify.ts, runSkilifyCommand -> runSkillifyCommand
• 16 claude-code/tests/skilify-*.test.ts files renamed
• Tree-wide case-aware text replace across src/, openclaw/, pi/extension-source/, .github/workflows/, README, RELEASE_CHECKLIST, esbuild.config.mjs, vitest.config.ts, hook tests
• Stale <agent>/bundle/skilify-worker.js artifacts removed; bundles regenerated to <agent>/bundle/skillify-worker.js

State directory auto-migration

New src/skillify/legacy-migration.ts: one-shot renameSync of ~/.deeplake/state/skilify/ -> ~/.deeplake/state/skillify/ on first boot of the renamed version. Wired into all four mkdirSync entry points (state.ts, scope-config.ts, manifest.ts, auto-pull.ts). EXDEV/EPERM falls back to leaving the legacy dir in place.

OpenClaw is a self-contained bundle that can't import from src/skillify/, so the migration is inlined into openclaw/src/index.ts and called before the existing fsMkdir on the state dir — once the new dir exists the migration becomes a no-op and any legacy data would be orphaned.

Tests

New claude-code/tests/skillify-legacy-migration.test.ts (5 tests): legacy-missing, current-already-exists (no clobber), happy-path rename preserving config.json/pulled.json/per-project state, idempotent re-call (module-level attempted flag), and renameSync EXDEV swallowed.

Audit

After the rename, the only skilify references in the tree are 4 intentional string literals (the migration helper's legacy-path target, the inlined openclaw copy, JSDoc, and a test fixture) plus their 18 esbuild compilations in bundle/. Zero filenames, zero camelCase/PascalCase identifiers.

Risk

Users with hivemind skilify aliases / scripts get a hard error after upgrade. State directory auto-migrates so installed-skill manifests, scope config, and per-project state survive without manual intervention. If renameSync fails (cross-device link, perms), the legacy dir stays put and the new dir starts fresh — pull repopulates pulled.json, but unpull of pre-rename installs may need manual cleanup.

Sequencing

Originally planned to wait for #112 to merge to avoid conflicts; #112 has since landed plus follow-ups (autopull throttle removal, maybeAutoPull -> autoPullSkills rename, README condensed into docs/SKILLIFY.md). Branch was based on the pre-merge tip of #112 and merged with origin/main afterward; conflicts in auto-pull.ts, the four session-start.ts files, the CLI USAGE block, two test files, README, and 6 bundle outputs are resolved in 148337d.

Test plan

• [ ] npm test green (2184/2184 in CI)
• [ ] npm run build produces all 12 + 10 + 9 + 9 + 1 + 1 + 1 + 1 bundles
• [ ] After upgrade on a machine with a populated ~/.deeplake/state/skilify/, the directory has been renamed in place to ~/.deeplake/state/skillify/ on the first SessionStart and installed pulled skills still resolve
• [ ] hivemind skilify (legacy spelling) returns Unknown command: skilify
• [ ] hivemind skillify works as documented

Summary by CodeRabbit

• Bug Fixes

  • Corrected skill management command spelling from skilify to skillify throughout the system.
  • Added automatic legacy state directory migration that renames older ~/.deeplake/state/skilify to ~/.deeplake/state/skillify on first run.
  • Fixed module import paths and worker bundle references to use correct skillify naming.

• Chores

  • Updated build configuration and test files to reference corrected module paths and naming conventions.