Slash commands let you run hooks and pull in steering files on demand, directly from the chat. Type / in the chat input to see available commands and execute them instantly.
Hooks with manual triggers appear in the slash command menu. When you select a hook, Kiro executes it immediately in your current session. Here are some examples of hooks you might create:
| Command | Description |
|---|---|
/sync-source-to-docs | Syncs source file changes to documentation |
/run-tests | Executes your configured test suite |
/generate-changelog | Creates changelog from recent commits |
Steering files configured with manual inclusion appear as slash commands. Unlike always-on steering that's automatically included in every conversation, manual steering files let you pull in specific guidance only when you need it. When selected, the file's contents are added to your current conversation context. Here are some examples:
| Command | Description |
|---|---|
/accessibility | Accessibility guidelines for UI components |
/code-review | Code review checklist and feedback principles |
/performance | React and Next.js performance optimization tips |
/refactor | Refactoring rules and common patterns |
/testing | Testing standards and Jest/RTL conventions |
To add a hook as a slash command, set its trigger type to Manual. See Hook types for details.
To add a steering file as a slash command, set inclusion: manual in the frontmatter. See Steering for configuration options.
/ in the chat input field/run-e2e-tests or /accessibility make commands easy to find# providers — Slash commands work alongside context providers for maximum control
Slash commands