{"version":"2.1.277","anchor":"skill-discovery-now-also-checks-the-primary-worktree-when-ru","canonical_anchor":"skill-discovery-now-also-checks-the-primary-worktree-when-ru","heading":"Skill discovery now also checks the primary worktree when running from a linked git worktree","tier":"notice","area":"Skills","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/skill-discovery-now-also-checks-the-primary-worktree-when-ru","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### Skill discovery now also checks the primary worktree when running from a linked git worktree\n\nSkill discovery now also checks the main worktree's .claude\/skills folder when run from a linked git worktree\n\n**What**\n\nWhen 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.\n\n**Why**\n\nPreviously, 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.\n\n- Area: Skills\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}