{"version":"2.1.289","anchor":"hook-skipped-message-wording-differs-for-unapplied-hooks","canonical_anchor":"hook-skipped-message-wording-differs-for-unapplied-hooks","heading":"Plugin hook skip notices worded differently when a hook was not applied","tier":"notice","area":"Plugin Hooks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.289\/e\/hook-skipped-message-wording-differs-for-unapplied-hooks","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.289","markdown":"### Plugin hook skip notices worded differently when a hook was not applied\n\nWhen a plugin hook was not applied, the notice now gives the reason directly instead of saying the hook was skipped\n\n**Unclear.** When a hook counts as not applied is not known.\n\n**What**\n\nA hook is a piece of plugin code that runs at set moments. When one does not run, Claude Code shows a notice. If the hook was not applied, the notice now reads as the plugin's name, the event and the reason. In other cases it still says the hook \"was skipped\". The notice also now uses the right value where before it referred to the wrong one.\n\n**Why**\n\nPlugin hook errors are clearer about what happened.\n\n- Area: Plugin Hooks\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}