{"version":"2.1.295","anchor":"skills-sync-removes-stale-hooks-and-tracks-removal-attempts","canonical_anchor":"skills-sync-removes-stale-hooks-and-tracks-removal-attempts","heading":"Skills sync now cleans up hooks left behind by removed skills","tier":"notice","area":"Skills","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/skills-sync-removes-stale-hooks-and-tracks-removal-attempts","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Skills sync now cleans up hooks left behind by removed skills\n\nAfter syncing skills, Claude Code now removes leftover hooks for skills that were removed, and logs a warning if that fails\n\n**What**\n\nSkills are packaged instructions and tools that Claude Code can load. Some are kept up to date by a sync step. At the end of each sync, Claude Code now runs a cleanup that takes into account the skill folders it found and the folders it tried to remove. If the cleanup fails, Claude Code logs a warning.\n\n**Why**\n\nHooks, which are actions that run automatically at set moments, could belong to a synced skill that has since been removed. They are now cleaned up rather than left behind.\n\n- Area: Skills\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}