Git and commit messages
WhoseDev integrates with the built-in Source Control view. When you stage changes, you can ask WhoseDev to draft a commit message from the diff.
Generate a commit message
Section titled “Generate a commit message”- Stage the files you want to commit in the Source Control view.
- Click the sparkle (Generate Commit Message) control in the commit message input, or run WhoseDev: Generate Commit Message (
whosedev.git.generateCommitMessage) from the Command Palette.
WhoseDev reads staged file diffs (up to 40 files per generation), summarizes the change, and writes a Conventional Commits-style message into the commit input.
Review before committing
Section titled “Review before committing”Always read the generated message before you commit. The generator infers intent from diffs but may miss breaking changes, security-sensitive edits, or ticket references your team requires.
Edit the message to add issue IDs, co-authors, or breaking-change footers as needed.
Requirements
Section titled “Requirements”- Staged changes must be present — an empty index produces no useful message.
- The feature uses your currently selected AI route (managed, BYOK, or local, depending on configuration and availability).