hooks-setup

Configure Claude Code lifecycle hooks for iEvo events and notifications.

Updated May 17, 2026
One-click install
npx skills add https://github.com/ievo-ai/skills --skill hooks-setup-ievo-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hooks-setup
Source: https://github.com/ievo-ai/skills/tree/main/plugins/ievo/skills/hooks-setup
Command: npx skills add https://github.com/ievo-ai/skills --skill hooks-setup-ievo-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the configuration of Claude Code lifecycle hooks for iEvo events, allowing for automated notifications and updates.

Core Features & Use Cases

  • Automated Lifecycle Hook Setup: Configure Claude Code hooks for iEvo events such as init complete, security RED verdict, and evolution captured.
  • Custom Notification Preferences: Choose between terminal bell, desktop notifications, custom scripts, or no notifications.
  • Project or Global Scope: Set hooks to apply to project-specific or global Claude Code sessions.
  • Version Checking: Optional version-check nudge to inform users when the iEvo plugin is out of date.

Quick Start

To configure hooks for iEvo events, use the command: /ievo:hooks-setup

Frequently Asked Questions about hooks-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up Claude Code lifecycle hooks for automated notifications?

You can configure Claude Code lifecycle hooks for automated notifications by running the `/ievo:hooks-setup` command, which streamlines setup for iEvo events like init complete and security verdicts.

What are Claude Code lifecycle hooks and when do I need them?

Claude Code lifecycle hooks are triggers that respond to specific events such as init complete, security RED verdict, or evolution captured, allowing you to automate notifications and version checking.

Does Claude Code lifecycle hook setup require a specific version?

Yes, lifecycle hook setup requires Claude Code version 2.1.139+ for basic functionality, and version 2.1.141+ or higher if you want to enable desktop notifications.

Can I configure Claude Code hooks to apply globally instead of just to a project?

Yes, during the hook setup process you can choose whether the lifecycle hooks apply to project-specific Claude Code sessions or globally across all your sessions.

What notification options are available when automating Claude Code lifecycle hooks?

When automating lifecycle hooks, you can choose between terminal bell alerts, desktop notifications, custom scripts, or disable notifications entirely based on your preferences.

What's the best way to check if my iEvo plugin is out of date?

The lifecycle hook setup process includes an optional version-check nudge feature that informs you when the iEvo plugin is out of date during your Claude Code sessions.