commit-review

You can generate conventional commit messages by requesting a review of your current staged and unstaged code changes, which automatically groups edits into atomic, revertable commits based on their intent. This ensures your git history is clean and searchable.

Commit message generation with custom commitlint rules works by automatically scanning your repository for commitlint config, existing git log patterns, and custom commit shapes. This ensures generated messages match your local standards exactly without manual guesswork.

Yes, automated commit messages support monorepo and single-app codebases by organizing changes into atomic, revertable commits based on the purpose of edits. It applies custom commit conventions and excludes sensitive files from proposals across complex structures.

The best way to group code changes into atomic commits is through intent-based grouping, which organizes staged and unstaged edits by their purpose rather than file paths. This produces production-grade conventional commits perfectly formatted for pull requests.

To avoid vague commit messages on a large feature branch, the review process pulls relevant session context to understand the reasoning behind changes. This context-aware approach ensures your git history avoids misleading or uninformative entries for older branches.

No, you do not need to manually exclude sensitive files when generating git commit messages. The automated review process inherently handles the exclusion of sensitive files from commit proposals, ensuring secure and compliant repository updates.