{"version":"2.1.304","anchor":"session-hook-removal-scoped-by-skill-root","canonical_anchor":"session-hook-removal-scoped-by-skill-root","heading":"Removing one skill's hooks no longer removes another skill's","tier":"notice","area":"Hooks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/session-hook-removal-scoped-by-skill-root","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Removing one skill's hooks no longer removes another skill's\n\nRemoving session hooks can now be limited to those added by one skill, so identical hooks added by other skills stay in place\n\n**What**\n\nA hook is an action set up to run automatically at certain points while Claude Code works. A skill is a packaged set of instructions Claude Code can load, and a skill can add hooks for the length of a session (a single working conversation).\n\nWhen session hooks are removed, the removal can now be limited to hooks that came from one particular skill's folder. Before, it removed matching hooks everywhere. Clearing all session hooks now also clears one more piece of stored state.\n\n**Why**\n\nRemoving one skill's hooks no longer removes identical hooks that a different skill added.\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}