Answer: The Kiro hook configuration schema requires a version field (currently "v1"), and each hook requires a name and a trigger, with optional matcher and action fields. The action requires a type of command or agent, with a command or prompt depending on the type. Status: Confirmed Entry: tool/kiro/settings/hook-schema Revision: 2 Digest: sha256:45cbd4459e670ff3 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:43:12Z Last changed: 2026-11-20T13:30:10Z (hooks[].action.prompt: Cond. → Agent prompt to inject) Last verified: 2026-11-20T13:30:10Z Next check: 2026-11-21T13:30:10Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of version | v1 | [1] | 2026-11-20 hooks[].name | Unique identifier for the hook | [1] | 2026-11-20 hooks[].trigger | Event trigger name in PascalCase | [1] | 2026-11-20 hooks[].matcher | Regex pattern matched against the event subject | [1] | 2026-11-20 hooks[].action.type | command or agent | [1] | 2026-11-20 hooks[].action.command | Shell command to run | [1] | 2026-11-20 hooks[].action.prompt | Agent prompt to inject | [1] | 2026-11-20 Sources: [1] Amazon Web Services. "Hooks - What's new in 1.0 - IDE 1.x - Docs - Kiro". https://kiro.dev/docs/ide/whats-new-v1/hooks/ Role: primary. Accessed: 2026-11-20T13:30:10Z Quote: "Schema version — currently "v1"" (Supports: version) Quote: "hooks[].name Yes Unique identifier for the hook" (Supports: hooks[].name) Quote: "hooks[].trigger Yes Event trigger name in PascalCase" (Supports: hooks[].trigger) Quote: "hooks[].matcher No Regex pattern matched against the event subject" (Supports: hooks[].matcher) Quote: "hooks[].action.type Yes Action type: command or agent" (Supports: hooks[].action.type) Quote: "hooks[].action.command Cond. Shell command to run" (Supports: hooks[].action.command) Quote: "hooks[].action.prompt Cond. Agent prompt to inject" (Supports: hooks[].action.prompt) Published: 2026-11-20T07:39:25Z Snapshot SHA-256: a3b53c87953ed79290f7d80c216a01c825ecbc9f0f39b1f4cd7df96e71acaa8d (captured 2026-11-20T13:30:07Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. Cross-check: not-available at 2026-11-20T13:30:10Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:30:10Z Last attempt: 2026-11-20T13:30:10Z Notes and limitations: Extracted automatically from a single official source (section "Schema details"). Related: https://latestn.com/tool/kiro/settings/import-export-configuration How do I import or export my Kiro Crew configuration? https://latestn.com/tool/kiro/settings/import-profile-to-kiro How do I import a profile into Kiro? https://latestn.com/tool/kiro/settings/java-custom-steering-files How do I create custom steering files for a Java project in Kiro? https://latestn.com/tool/kiro/settings/global-ignore-files How do I create a global .kiroignore file that applies to all Kiro workspaces? https://latestn.com/tool/kiro/settings/gui-diff-tools How do I set up a GUI diff tool like a visual editor in Kiro CLI? https://latestn.com/tool/kiro/settings/hook-file-location Where should Kiro hook files be named and located? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-20T13:30:10Z | changed | hooks[].action.prompt: Cond. → Agent prompt to inject | [1] 2026-11-20T13:30:10Z | changed | hooks[].action.command: Cond. → Shell command to run | [1] 2026-11-20T13:30:10Z | changed | hooks[].matcher: No → Regex pattern matched against the event subject | [1] 2026-11-20T13:30:10Z | changed | hooks[].trigger: Yes → Event trigger name in PascalCase | [1] 2026-11-20T13:30:10Z | changed | hooks[].name: Yes → Unique identifier for the hook | [1] 2026-11-13T03:43:12Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/kiro/settings/hook-schema/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/kiro/settings/hook-schema POST: https://latestn.com/dispute/tool/kiro/settings/hook-schema with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/kiro/settings/hook-schema?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). What is the schema for a Kiro hook configuration? Revision 2, last verified 2026-11-20T13:30:10Z. https://latestn.com/tool/kiro/settings/hook-schema (accessed 2026-11-21T09:53:38Z). @misc{LatestN_tool_kiro_settings_hook_schema_r2, title = {What is the schema for a Kiro hook configuration?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/kiro/settings/hook-schema}}, note = {Revision 2; digest sha256:45cbd4459e670ff3; last verified 2026-11-20T13:30:10Z; accessed 2026-11-21T09:53:38Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/kiro/settings/hook-schema