claude-code - 💡(How to fix) Fix Claude Code ignores its own safety hooks — violation #80 [1 comments, 2 participants]

TL;DR

Modify the PreToolUse hooks to require explicit acknowledgment of warnings before proceeding with edits.

Guidance

• Review the implementation of PreToolUse hooks to ensure they are designed to block or interrupt the editing process when warnings are triggered, rather than simply injecting warnings as context.
• Investigate how Claude's model is interpreting hook output and determine why it is treating warnings as skippable context instead of mandatory gates.
• Consider adding a mechanism for explicit acknowledgment of warnings, such as a confirmation prompt or a required response to a warning message, before allowing the edit to proceed.
• Examine the integration of the Harmonic Code Council (HCC) review warnings and Approach tracking warnings to ensure they are properly linked to the PreToolUse hooks and are being correctly interpreted by Claude's model.

Example

No code snippet is provided as the issue does not contain sufficient technical details to generate a specific example.

Notes

The provided information suggests a structural issue with how warnings are handled within the system, and resolving this will likely require changes to the underlying architecture or the integration of the PreToolUse hooks with Claude's model.

Recommendation

Apply a workaround by modifying the PreToolUse hooks to require explicit acknowledgment of warnings, as this addresses the core issue of Claude ignoring warnings and proceeding with edits without proper validation.