Problem
The “Generate Message” feature currently produces generic output and does not allow customization. Users who follow specific commit message standards or project-wide rules cannot configure how the generated message should be structured. This leads to inconsistent commit messages, reduced clarity, and additional manual editing every time the button is used.
What problem does this solve?
It enables users to define their own formatting rules or templates for the “Generate Message” button so that the generated output always matches project standards (e.g., commit message conventions, documentation style, or structured text requirements). This removes repetitive manual cleanup and increases productivity.
Solution
Introduce a “Message Generation Rules” or “Custom Template” configuration that allows users to define how the “Generate Message” button should construct its output. The rule system could support variables (e.g., file name, diff summary, change type), conditional blocks, and static text. Once configured, clicking the button would automatically generate a message that follows the user’s predefined structure.
How should it work?
-
Add a new settings section such as “Generate Message Rules”.
-
Allow the user to enter a custom template (plain text or lightweight templating syntax).
-
When “Generate Message” is clicked, Qoder applies the defined rule/template and fills in dynamic fields.
-
Output is inserted directly into the commit message input.
This makes the feature predictable, customizable, and aligned with team standards.
Use Case
A developer working in a team that uses a strict commit message format wants every generated message to follow the same structure (e.g., feature description, technical impact, ticket number, change type). Instead of rewriting the output every time, the template ensures consistency and speed.
Another scenario: users write documentation, notes, review summaries, or test logs and want the generator to follow a repeatable pattern.
When would you use this?
Whenever the user clicks the “Generate Message” button and wants the output to automatically conform to their predefined style without needing manual editing.
Priority
Medium – Important improvement
This feature significantly improves workflow consistency and reduces repetitive manual work, though it does not block core functionality.
Additional Info
(Optional)
Examples of possible rule/template formats:
-
Custom commit message structure
-
Structured bug report templates
-
Code review summary format
-
Release note generation template
This feature would bring Qoder closer to advanced IDE assistants and improve its usability for professional teams who rely on consistent standards.
