Hooks 🪝 to execute predefined Agent tasks - From Kiro IDE

[sFritsch09]

Current Limitation:

Zed supports spawning (and rerunning) commands via its integrated terminal, with output visible there. These commands can access a limited subset of Zed state, like the current file path or selected text. However, there's no built-in way to trigger AI agent tasks based on IDE events (e.g., pre-commit), limiting context-aware automation.

Proposed Feature: Introduce AI Hooks

Add Hooks to Zed: event-triggered mechanisms that execute predefined AI agent prompts in response to IDE state changes, such as file saves or Git pre-commits. This goes beyond terminal commands by integrating AI for intelligent outputs like generated commit messages.

• What are Hooks? Per kiro.dev/docs/hooks, hooks respond to events (e.g., state changes) by running custom logic, often via an AI agent.
• Hook Types: As in kiro.dev/docs/hooks/types, they include triggers (e.g., git:pre-commit), agent prompts, context (e.g., file diffs), and outputs (e.g., commit messages). See examples at kiro.help/docs/kiro/hooks/examples.

Key Use Case: Smart Git Commit Messages

Users want customizable prompts for AI-generated commits. Example hook config:

{
  "name": "smart-commit-message",
  "description": "Generate descriptive commit messages from staged changes",
  "trigger": { "type": "git:pre-commit" },
  "agent": {
    "prompt": "Analyze staged changes and generate a conventional commit message: type(scope): description\n\nTypes: feat, fix, etc.\nFocus on WHAT and WHY.",
    "context": ["staged-changes", "file-diffs", "commit-history"],
    "output": { "type": "commit-message" }
  },
  "enabled": true
}

Benefits:

• Automates context-aware tasks like commit message generation.
• Customizable prompts for user-defined workflows.
• Enhances productivity by reacting to events (e.g., pre-commit) with AI.

This would make Zed more AI-integrated and event-responsive. Implementation could use a config file like .zed/hooks.json.