Skip to content

Comments

feat: support project-scoped lockfiles and renamed skill installs#369

Open
farnoodma wants to merge 2 commits intovercel-labs:mainfrom
farnoodma:feat/rename-scoped-updates-signed
Open

feat: support project-scoped lockfiles and renamed skill installs#369
farnoodma wants to merge 2 commits intovercel-labs:mainfrom
farnoodma:feat/rename-scoped-updates-signed

Conversation

@farnoodma
Copy link

Summary

This PR implements the two CLI capabilities requested around update tracking and rename support:

  • Project + global lock scope support

    • skills add now tracks installs in both scopes:
      • project: <cwd>/.agents/.skill-lock.json
      • global: ~/.agents/.skill-lock.json
    • skills check / skills update now read both scopes by default.
    • Added explicit scope flags:
      • --project / -p: project only
      • --global / -g: global only
  • --rename support for installs

    • Added --rename <name> to skills add for single-skill installs.
    • Rename applies to:
      • installation folder name
      • name frontmatter in installed SKILL.md
    • Guardrail: --rename fails when multiple skills are selected.
  • Rename-aware updates

    • skills update preserves local installed names by reinstalling with --rename <installed-name>.
    • This ensures skills installed from source X as local alias Y stay as Y after updates.

Implementation Notes

  • Split into two commits for review clarity:
    1. feat: track and update skills in project and global scopes
    2. feat: add renamed skill installs and preserve aliases on update
  • Updated docs/help text in README.md, AGENTS.md, and CLI help output.
  • Added focused tests for scope parsing/behavior, lock scope behavior, and rename install behavior.

Test plan

  • pnpm install --frozen-lockfile
  • pnpm build
  • pnpm format:check
  • pnpm test
  • node scripts/validate-agents.ts

@vercel
Copy link

vercel bot commented Feb 15, 2026

@farnoodma is attempting to deploy a commit to the Vercel Team on Vercel.

A member of the Team first needs to authorize it.

@farnoodma
Copy link
Author

farnoodma commented Feb 15, 2026

@quuu this PR adds project-scoped lock tracking + --rename support with full test coverage. Would appreciate your review when you have a moment.

@farnoodma farnoodma force-pushed the feat/rename-scoped-updates-signed branch from 7f18723 to 5ba949f Compare February 21, 2026 07:57
@farnoodma
Copy link
Author

@chibicode @nicoalbanese quick ping: this PR has been open since Feb 15 (almost a week), and this change is needed for our use-cases (project-scoped lockfiles + renamed installs preserved on update). I’d really appreciate a review when you have a moment.

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