ai-hooks-integration

Normalize AI hook events across Claude Code, Gemini CLI, Cursor, and OpenCode.

11|2|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/runkids/my-skills --skill ai-hooks-integration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ai-hooks-integration
Source: https://github.com/runkids/my-skills/tree/main/ai-hooks-integration
Command: npx skills add https://github.com/runkids/my-skills --skill ai-hooks-integration

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill unifies and stabilizes AI hooks across Claude Code, Gemini CLI, Cursor, and OpenCode by normalizing events and filtering noise.

Core Features & Use Cases

  • Cross-tool lifecycle hook orchestration with canonical event formats.
  • Noise filtering and unified source detection to prevent duplicate events.
  • Use Case: Streamline security policies, formatting, and notifications across toolchains.

Quick Start

To begin, install unified hooks across Claude, Gemini, Cursor, and OpenCode using the provided scripts, connect a handler, and verify that events are normalized to the canonical format. Then add or remove hooks with the merge and remove utilities and test with a dry run before applying changes.

Frequently Asked Questions about ai-hooks-integration

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

FAQPage Schema
How do I normalize AI hooks across Claude Code, Gemini CLI, Cursor, and OpenCode?

Cross-tool hook normalization unifies events from multiple AI tools into a canonical format, eliminating duplicate events and inconsistent handling. Install unified hooks using provided scripts, connect a handler to receive normalized events, and verify output matches the canonical contract before deploying to your toolchain.

Can I enforce consistent security policies and formatting rules across different AI tools?

Yes. This Skill applies unified security policies, auto-formatting, and notifications across Claude Code, Gemini CLI, Cursor, and OpenCode by routing all tool events through normalized hooks. Define policies once and enforce them idempotently across your entire AI tool stack.

What's the best way to test hook changes before applying them to production?

Test hook changes with a dry-run mode before merging. The Skill includes merge and remove utilities that validate changes against the canonical event contract, ensuring idempotent application and preventing duplicate or conflicting hooks across tools.

How do I prevent duplicate events when using multiple AI tools together?

Noise filtering and unified source detection identify and suppress duplicate events fired by multiple tools. Normalized events expose their source tool, allowing handlers to deduplicate or route based on origin while maintaining a single event contract.

Does this work if I'm adding hooks to an existing toolchain with mixed tool versions?

Yes. The Skill enforces idempotent merges, meaning repeated installations of the same hooks produce consistent results regardless of existing state. Merge utilities check for conflicts and apply changes safely across tools running different versions.