Skip to content

fix: Fix three bugs making hookify plugin non-functional#29522

Closed
0xLeathery wants to merge 1 commit intoanthropics:mainfrom
0xLeathery:fix/hookify-plugin-bugs
Closed

fix: Fix three bugs making hookify plugin non-functional#29522
0xLeathery wants to merge 1 commit intoanthropics:mainfrom
0xLeathery:fix/hookify-plugin-bugs

Conversation

@0xLeathery
Copy link

Summary

Fixes #28299, #20749, #20747

Test plan

  • All 6 modified Python files pass syntax validation (ast.parse)
  • from core.config_loader import load_rules, extract_frontmatter, Rule succeeds from plugin root
  • from core.rule_engine import RuleEngine succeeds from plugin root
  • Install hookify as a plugin and verify hooks no longer print Hookify import error: No module named 'hookify'
  • Create a rule file in ~/.claude/ and verify it loads from a non-$HOME working directory
  • Trigger a warning rule and verify the model sees and responds to the warning via additionalContext

🤖 Generated with Claude Code

, #20747)

Fix broken Python imports by changing `from hookify.core.X` to `from core.X`
since PLUGIN_ROOT points directly to the hookify directory. Use absolute path
for rule file discovery so rules load from any CWD. Add hookSpecificOutput
with additionalContext to warning responses so the model sees warnings.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Hookify plugin: broken Python imports in hook scripts

1 participant