[BUG] hookify plugin: Python import error - "No module named 'hookify'"

Resolved 💬 5 comments Opened Dec 9, 2025 by cfdude Closed Dec 10, 2025

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

The hookify plugin fails with import errors when hooks execute:
Stop says: Hookify import error: No module named 'hookify'

What Should Happen?

UserPromptSubmit:Callback hook succeeded: Success

Error Messages/Logs

Stop says: Hookify import error: No module named 'hookify'

Steps to Reproduce

Root Cause:

The Python scripts in hooks/ use imports like:
from hookify.core.config_loader import load_rules
from hookify.core.rule_engine import RuleEngine

But the plugin cache structure is:
~/.claude/plugins/cache/claude-code-plugins/hookify/0.1.0/
├── core/
│ ├── __init__.py
│ ├── config_loader.py
│ └── rule_engine.py
├── hooks/
│ ├── stop.py
│ └── ...

There's no hookify/ subdirectory, so Python can't resolve the imports.

Workaround:

Create a symlink in the plugin root:
cd ~/.claude/plugins/cache/claude-code-plugins/hookify/0.1.0
ln -s . hookify

Suggested Fix:

Either:

  1. Change imports to relative: from core.config_loader import ...
  2. Or restructure the plugin to include hookify/ package directory

Environment:

  • macOS
  • Claude Code (latest)
  • hookify v0.1.0

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.0.62

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

iTerm2

Additional Information

_No response_

View original on GitHub ↗

This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗