claude-code - 💡(How to fix) Fix PreToolUse hook `if` pattern does not match commands chained with `&&` or `;` [1 participants]

• Warn when a Bash call contains a command that would match a hook pattern but is skipped due to chaining

TL;DR

Modify the if pattern in the PreToolUse hook configuration to support substring or regex matching to correctly identify commands within a chained sequence.

Guidance

• Consider updating the if pattern to use a substring match, such as Bash(*git commit*), to ensure the hook fires when git commit appears anywhere in the command string.
• Alternatively, modify the hook configuration to match each individual command in a &&/;/|| chain, rather than just the full string.
• To mitigate the issue, users can temporarily avoid chaining commands with && and instead run each command separately to ensure hooks are triggered as expected.
• Investigate adding a warning or log message when a hook is skipped due to pattern mismatch to improve visibility into hook behavior.

Example

{
  "type": "command",
  "if": "Bash(*git commit*)",
  "command": "bash .claude/hooks/guard-commit-lint.sh",
  "statusMessage": "Running pre-commit checks..."
}

Notes

The proposed solution relies on modifying the if pattern to support substring matching, which may require updates to the underlying hook configuration parser. Additionally, the issue may be resolved by modifying the hook to match individual commands in a chain, but this approach may require significant changes to the hook implementation.

Recommendation

Apply workaround by modifying the if pattern to use substring matching, as this approach is likely to be easier to implement and test than modifying the hook to match individual commands in a chain.