Skip to content
This repository was archived by the owner on Jan 14, 2026. It is now read-only.

Conversation

@jinzhongjia
Copy link
Owner

Add the prompt_template setting to allow customization of the prompt. Supports %{language}, %{diff}, and %{history_context} placeholders. Move the default prompt from git_utils.lua to config.lua.

Add the prompt_template setting to allow customization of the prompt.
Supports %{language}, %{diff}, and %{history_context} placeholders.
Move the default prompt from git_utils.lua to config.lua.
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @jinzhongjia, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly enhances the flexibility of the git commit message generation feature by allowing users to define and utilize custom prompt templates. This change empowers users to tailor the AI's commit message output to their specific needs and conventions, moving the system towards greater configurability and user control.

Highlights

  • Custom Prompt Templates: Introduced a new prompt_template setting that allows users to define their own templates for generating git commit messages.
  • Placeholder Support: The custom prompt templates support dynamic placeholders: %{language}, %{diff}, and %{history_context}.
  • Default Prompt Relocation: The default commit message prompt has been moved from git_utils.lua to config.lua for easier management and customization.
  • Enhanced Test Coverage: New test cases have been added to verify the correct functionality of custom prompt templates and placeholder replacement.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces a great new feature allowing users to customize the git commit prompt via templates. The implementation is solid, moving the default prompt to the configuration and adding comprehensive documentation and tests. I have one suggestion in git_utils.lua to improve the robustness of placeholder replacement. Overall, this is a well-executed feature addition.

end

local prompt = template
prompt = prompt:gsub("%%{language}", lang or "English")
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

For consistency and to prevent potential issues if a language name contains special gsub characters (like %), it's safer to use a function for the replacement here, just as you've done for %{diff} and %{history_context}. This ensures that the lang string is treated as a literal replacement and avoids unintended behavior from string.gsub's replacement string parsing.

  prompt = prompt:gsub("%%{language}", function() return lang or "English" end)

Wrap the language placeholder replacement in a function to prevent Lua
from interpreting special characters in the `lang` variable.
@jinzhongjia jinzhongjia merged commit fcb1394 into main Jan 4, 2026
1 check passed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants