fix(hookify): use relative imports for Python module resolution #13437
+10
−10
Conversation
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
The hookify plugin's Python hook scripts use absolute imports like `from hookify.core.config_loader` which fail because: 1. PLUGIN_ROOT is added to sys.path (e.g., .../hookify/0.1.0/) 2. Python looks for hookify/core/ inside PLUGIN_ROOT 3. But there's no hookify/ subdirectory - core/ is directly in PLUGIN_ROOT This causes 'No module named hookify' error on all platforms. Fix: Change to relative imports `from core.config_loader` which correctly resolve since PLUGIN_ROOT contains core/ directly. Files changed: - hooks/pretooluse.py - hooks/posttooluse.py - hooks/stop.py - hooks/userpromptsubmit.py - core/rule_engine.py Fixes anthropics#13426 Fixes anthropics#13427
|
Paste this to Claude Code: |
kmk142789
approved these changes
Dec 15, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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
The hookify plugin fails with 'No module named hookify' error on all platforms.
Root Cause
Scripts use absolute imports like 'from hookify.core.config_loader' but PLUGIN_ROOT contains core/ directly, not in a hookify/ subdirectory.
Fix
Change to relative imports: 'from core.config_loader' which correctly resolve since PLUGIN_ROOT contains core/ directly.
Files Changed
Fixes #13426
Fixes #13427