hooks-daemon
npx machina-cli add skill Edmonds-Commerce-Limited/claude-code-hooks-daemon/hooks-daemon --openclawHooks Daemon Management
Manage your Claude Code Hooks Daemon installation with these commands.
Available Commands
Upgrade Daemon
Update to a new version of the hooks daemon:
/hooks-daemon upgrade # Auto-detect and upgrade to latest version
/hooks-daemon upgrade 2.14.0 # Upgrade to specific version
/hooks-daemon upgrade --force # Force reinstall current version
See upgrade.md for detailed upgrade documentation.
Restart Daemon
Required after editing .claude/hooks-daemon.yaml or project handlers:
/hooks-daemon restart
The daemon caches config at startup β restart picks up any config or handler changes.
See restart.md for details.
Check Health & Status
Verify daemon is running correctly:
/hooks-daemon health # Quick health check
/hooks-daemon logs # View last 50 lines of logs
/hooks-daemon logs --follow # Stream logs in real-time
See health.md for health check details.
Develop Project Handlers
Scaffold new project-level handlers:
/hooks-daemon dev-handlers # Interactive handler scaffolding
See dev-handlers.md for handler development guide.
Quick Start
After editing .claude/hooks-daemon.yaml:
/hooks-daemon restart # Apply config changes
/hooks-daemon health # Verify it's running
If you're experiencing issues:
# 1. Check daemon status
/hooks-daemon health
# 2. View recent logs
/hooks-daemon logs
# 3. Generate a bug report with full diagnostics
/hooks-daemon bug-report "description of the issue"
# 4. Restart to recover
/hooks-daemon restart
Troubleshooting
See references/troubleshooting.md for common issues and solutions.
Implementation
Parse subcommand and route to appropriate script:
# Get skill directory (where this SKILL.md is located)
SKILL_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
# Parse subcommand from $ARGUMENTS
SUBCOMMAND="${1:-help}"
shift || true # Remove subcommand from arguments
# Route to appropriate script
case "$SUBCOMMAND" in
upgrade)
bash "$SKILL_DIR/scripts/upgrade.sh" "$@"
;;
health)
bash "$SKILL_DIR/scripts/health-check.sh" "$@"
;;
dev-handlers)
bash "$SKILL_DIR/scripts/init-handlers.sh" "$@"
;;
logs|status|restart|handlers|validate-config|bug-report)
# Forward to daemon CLI wrapper
bash "$SKILL_DIR/scripts/daemon-cli.sh" "$SUBCOMMAND" "$@"
;;
help|--help|-h|"")
# Show help (this SKILL.md content)
echo "Usage: /hooks-daemon <command> [args...]"
echo ""
echo "Available commands:"
echo " restart Restart daemon (required after config changes)"
echo " health Check daemon health and status"
echo " upgrade [VERSION] Upgrade daemon to new version"
echo " dev-handlers Scaffold new project handlers"
echo " logs [--follow] View daemon logs"
echo " status Show daemon status"
echo " handlers List loaded handlers"
echo " bug-report DESC Generate bug report with diagnostics"
echo ""
echo "After editing .claude/hooks-daemon.yaml, always run: /hooks-daemon restart"
echo ""
echo "For detailed documentation, see the skill files or run:"
echo " /hooks-daemon <command> --help"
;;
*)
echo "Error: Unknown subcommand: $SUBCOMMAND"
echo ""
echo "Usage: /hooks-daemon <command> [args...]"
echo "Run '/hooks-daemon help' for available commands."
exit 1
;;
esac
Note: All daemon management commands require manual user approval. The daemon will not auto-invoke these operations.
Source
git clone https://github.com/Edmonds-Commerce-Limited/claude-code-hooks-daemon/blob/main/src/claude_code_hooks_daemon/skills/hooks-daemon/SKILL.mdView on GitHub Overview
Hooks Daemon Management provides commands to upgrade the daemon, monitor health, restart after config changes, and scaffold project-level handlers. It centralizes routine maintenance for Claude Code Hooks Daemon installations.
How This Skill Works
The skill parses the requested subcommand and routes it to the corresponding script inside its directory. Supported commands include upgrade, health, dev-handlers, and a daemon CLI wrapper for logs and status.
When to Use It
- Upgrade the daemon to the latest or a specific version
- Apply config or handler changes and restart to pick them up
- Verify the daemon is healthy and view logs for troubleshooting
- Scaffold interactive project-level handlers for your projects
- Generate a diagnostic bug report to capture issues and diagnostics
Quick Start
- Step 1: After editing .claude/hooks-daemon.yaml, run /hooks-daemon restart
- Step 2: Run /hooks-daemon health to verify itβs running
- Step 3: If issues persist, view logs with /hooks-daemon logs or generate a bug report with /hooks-daemon bug-report description of the issue
Best Practices
- Always restart after editing .claude/hooks-daemon.yaml or project handlers
- Use health and logs commands to troubleshoot before making changes
- Specify a version for upgrades when you know the target release; use --force cautiously
- Prefer the interactive dev-handlers flow to scaffold correct project-level handlers
- When issues arise, use bug-report with a descriptive description and include relevant context
Example Use Cases
- /hooks-daemon upgrade
- /hooks-daemon upgrade 2.14.0
- /hooks-daemon restart
- /hooks-daemon dev-handlers
- /hooks-daemon logs --follow