Source Control

Kiro's Source Control view provides comprehensive Git integration with AI-enhanced features to streamline your version control workflow.

Kiro generates a commit message from your changes. If you have staged changes, the message describes only what is staged. If nothing is staged, the message describes the changes in your working tree, including the contents of new untracked files, and Kiro tells you so: Nothing is staged, so the commit message describes all changes. Large change sets are truncated before Kiro reads them, so stage a focused set when completeness matters.

View transcript: Demo of Kiro generating a git commit message

1. Stage the changes you want to commit. Or leave everything unstaged to describe your working-tree changes.
2. Select the 🪄 button next to the commit message field.
3. Review the generated message. Kiro analyzes your changes and creates a draft.
4. Edit the message if needed.
5. Commit your changes using the generated or edited message.

Tip: You can set up a custom keyboard shortcut for Kiro: Generate Commit Message in your keyboard settings for faster access.

• Files excluded by your ignore rules are left out by name and content. Kiro reports how many changed files it left out. If every changed file is excluded, Kiro tells you that no message was generated.
• Kiro refreshes the repository status first, so changes you just staged in a terminal are included.
• Kiro reads each included file's available diff, even when another changed file is excluded.
• Untracked files are described as new files with their content. Binary files and files larger than 1 MB are listed by name without their content.
• Kiro reads at most 8,000 characters of changes. Beyond that, the diff is cut off and marked as truncated, so later changes may not be described.
• If Kiro cannot read the repository's changes, it reports the reason instead of saying there are no changes.
• If there are no changes at all, Kiro says There are no changes to generate a commit message from.

Kiro follows the Conventional Commits format with detailed body sections:

<type>(<scope>): <subject>

- First change or addition
- Second change or improvement
- Third change if applicable
- Why this change was needed (if relevant)

• feat: New features
• fix: Bug fixes
• docs: Documentation changes
• style: Formatting changes
• refactor: Code restructuring
• test: Adding/updating tests
• chore: Maintenance tasks
• perf: Performance improvements
• ci: CI/CD changes

feat(docs): add comprehensive Source Control documentation
- Create new documentation page for Source Control features
- Update interface documentation to link to Source Control page
- Provide detailed explanation of AI-powered commit message generation
- Describe diff context provider and commit message generation process

You can include your current git changes in any chat conversation by typing #Git Diff. This allows Kiro to see your staged and unstaged changes, making it easier to get contextual help with your modifications.

Hey Kiro, can you fix the merge conflicts? #Git Diff

• Check your Git configuration and credentials
• Ensure you have proper permissions for the repository