[ENHANCEMENT] automatic commit generation

[KingingWang]

Problem (one or two sentences)

Does roo code currently support automatic commit generation? I don't seem to have found this feature, but Cline does support it. I hope roo code can add support for this as well.

Context (who is affected and when)

git commit

Desired behavior (conceptual, not technical)

When I am in the git commit plugin interface, there is a button that can generate commit information with one click

Constraints / preferences (optional)

No response

Request checklist

• I've searched existing Issues and Discussions for duplicates
• This describes a specific problem with clear context and impact

Roo Code Task Links (optional)

No response

Acceptance criteria (optional)

No response

Proposed approach (optional)

No response

Trade-offs / risks (optional)

No response

[roomote-v0]

I've analyzed this issue and here's my proposed implementation plan for adding automatic commit message generation:

Approach

VSCode's SCM API allows extensions to contribute buttons to the Source Control input box area. The plan is to register a new command that:

1. Reads the staged diff (or working directory diff if nothing is staged) using the existing git utilities in src/utils/git.ts
2. Sends the diff to the currently configured AI model with a system prompt requesting a conventional commit message
3. Writes the generated message into VSCode's SCM input box (vscode.scm.inputBox.value)

Implementation Details

1. Add a new command generateCommitMessage to the commandIds array in packages/types/src/vscode.ts
2. Register the command in src/activate/registerCommands.ts that:
   • Gets the staged diff via git diff --cached (falling back to git diff if nothing is staged)
   • Calls the configured AI provider with a focused prompt to generate a concise conventional commit message
   • Sets vscode.scm.inputBox.value with the result
3. Add an SCM menu contribution in src/package.json under contributes.menus["scm/title" to show a button in the Source Control title bar
4. Add the command contribution in src/package.json under contributes.commands with an appropriate icon (e.g., $(sparkle))
5. Add i18n strings for the command title and any UI text
6. Add tests covering the commit message generation flow

Key Considerations

• The feature will use the user's currently configured API provider and model, keeping it consistent with the rest of Roo Code
• The prompt will request conventional commit format (e.g., feat:, fix:, refactor:) for standardized output
• If no changes are detected, the command will show an informational message rather than calling the API
• The implementation will reuse existing infrastructure (API providers, git utilities) to minimize new code

Please mention @roomote in a comment saying that you approve this plan, and I'll proceed with the implementation.

[KingingWang]

@roomote I approve of this plan, and I think it would be even better if the model could be set individually per commit.

[roomote-v0]

Thanks for the approval! I've seen your comment about setting the model individually per commit -- that's a great idea. I'll explore adding a model picker option alongside the commit message generation. I'll open a draft PR to share progress shortly.

[roomote-v0]

Opened a draft PR with my attempt at addressing this: #11993

It includes per-commit model selection via a quick pick when multiple API profiles are configured. Feedback welcome!