Answer: To migrate Kiro CLI hooks to the current standalone file format, create a standalone .kiro/hooks/*.json file that wraps the same Hook definitions in a versioned document, using PascalCase trigger names when you create or revise a standalone Hook. Status: Confirmed Entry: tool/kiro/agents-and-automation/migrate-hooks-standalone-file-format Revision: 3 Digest: sha256:2b31612b37512c56 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:37:12Z Last changed: 2026-11-20T13:21:00Z (trigger naming: — → PascalCase) Last verified: 2026-11-20T13:21:00Z Next check: 2026-11-21T13:21:00Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of file format | .kiro/hooks/*.json | [1] | 2026-11-20 trigger naming | PascalCase | [1] | 2026-11-20 version | v1 | [1] | 2026-11-20 example trigger | PreToolUse | [1] | 2026-11-20 Sources: [1] Amazon Web Services. "Hooks migration - Upgrade from CLI 2.x - CLI - Docs - Kiro". https://kiro.dev/docs/cli/v3/hooks-migration/ Role: primary. Accessed: 2026-11-20T13:21:00Z Quote: "A standalone .kiro/hooks/*.json file wraps the same Hook definitions in a versioned document." (Supports: file format) Quote: "Use PascalCase trigger names when you create or revise a standalone Hook" (Supports: trigger naming) Quote: ""version" : "v1"" (Supports: version) Quote: ""trigger" : "PreToolUse"" (Supports: example trigger) Published: 2026-11-20T07:39:25Z Snapshot SHA-256: 42a3f96b2d7f54d28aae6bcb77671bf6460a3c962fd70e375b80accca0b06679 (captured 2026-11-20T13:21:00Z) 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:21:00Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:21:00Z Last attempt: 2026-11-20T13:21:00Z Notes and limitations: Extracted automatically from a single official source (section "Current standalone file format"). Related: https://latestn.com/tool/kiro/agents-and-automation/migrate-tool-matchers How do I migrate tool matchers in Kiro CLI hooks? https://latestn.com/tool/kiro/agents-and-automation/modify-thinking-behavior-mcp How can I modify Kiro's thinking behavior with MCP? https://latestn.com/tool/kiro/agents-and-automation/monitor-autonomous-mode-progress How do I monitor progress and review the pull request in Kiro autonomous mode? https://latestn.com/tool/kiro/agents-and-automation/migrate-hook-triggers How do I migrate Kiro hooks from 0.x trigger names to 1.0? https://latestn.com/tool/kiro/agents-and-automation/migrate-hooks How do I migrate my existing hooks to Kiro IDE 1.0? https://latestn.com/tool/kiro/agents-and-automation/migrate-hooks-profile-scoped-format How do I migrate Kiro CLI 2.x hooks to the current profile-scoped format? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-20T13:21:00Z | changed | trigger naming: — → PascalCase | [1] 2026-11-20T13:21:00Z | changed | trigger naming convention: PascalCase → — | [1] 2026-11-17T13:42:15Z | changed | example timeout: 30 → — | [1] 2026-11-13T03:37:12Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/kiro/agents-and-automation/migrate-hooks-standalone-file-format/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/agents-and-automation/migrate-hooks-standalone-file-format POST: https://latestn.com/dispute/tool/kiro/agents-and-automation/migrate-hooks-standalone-file-format with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/kiro/agents-and-automation/migrate-hooks-standalone-file-format?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I migrate Kiro CLI hooks to the current standalone file format? Revision 3, last verified 2026-11-20T13:21:00Z. https://latestn.com/tool/kiro/agents-and-automation/migrate-hooks-standalone-file-format (accessed 2026-11-21T10:08:12Z). @misc{LatestN_tool_kiro_agents_and_automation_migrate_hooks_standalone_file_format_r3, title = {How do I migrate Kiro CLI hooks to the current standalone file format?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/kiro/agents-and-automation/migrate-hooks-standalone-file-format}}, note = {Revision 3; digest sha256:2b31612b37512c56; last verified 2026-11-20T13:21:00Z; accessed 2026-11-21T10:08:12Z} } 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/agents-and-automation/migrate-hooks-standalone-file-format