You'll notice
Skill discovery now also checks the main worktree's .claude/skills folder when run from a linked git worktree
What
When Claude Code looks for available skills and commands and it's running inside a linked git worktree (a secondary working copy that shares history with a primary repository checkout), it now also checks the .claude/skills folder in the primary worktree if the current worktree doesn't have its own accessible one.
Why
Previously, skills defined only in a project's primary worktree could be invisible when working from a linked worktree. This change means skills set up for a project are found regardless of which worktree you're currently working in.
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agree
Fixed /plugin → Installed and /skills crashing when a skill or legacy command is named like a built-in Object property such as constructor…