Add prefix matching support for hooks#124
Merged
Merged
Conversation
Allow hooks to fire when a message starts with a specified string via a new `prefix` field, in addition to the existing exact-match `keyword` field. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
hooks設定にprefixフィールドを追加し、特定の文字列で始まるメッセージに対してコマンドを発火できるようにしたkeyword（完全一致）との AND 条件として動作するkeywordとprefixを同時指定した場合は両方の条件を満たすメッセージのみ反応する設定例
Test plan
npm test全55件パスprefixが一致した場合にコマンドが返ることprefixが一致しない場合にコマンドが返らないこと🤖 Generated with Claude Code