Skip to content

Scope skill lock files by install target - #12

Merged
cyhhao merged 1 commit into
mainfrom
fix/project-scoped-lockfile
May 30, 2026
Merged

Scope skill lock files by install target#12
cyhhao merged 1 commit into
mainfrom
fix/project-scoped-lockfile

Conversation

@cyhhao

@cyhhao cyhhao commented May 30, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Move default skill lock operations to project scope while preserving --global for user-level installs.
  • Apply the same scoped lock semantics to add, remove, check, update, and selected-agent persistence.
  • Migrate legacy global lock entries into a project lock only when the matching project skill directory exists.
  • Update docs and e2e coverage for project/global lock isolation.

Tests

  • npm test
  • npm run build
  • npm run test:e2e (196 passed, 1 skipped because the mutable production collection fixture returned not found)

Risk

  • Existing project installs tracked only in the old global lock are migrated on first project lock read when the installed canonical project skill exists.

@cyhhao
cyhhao merged commit 601af26 into main May 30, 2026
1 check passed
@cyhhao
cyhhao deleted the fix/project-scoped-lockfile branch May 30, 2026 05:41
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