Problem
When using Qoder’s auto-generate commit message feature (the green Q button in Git panel), the generated commit message does not follow the custom format defined in my .qoder/rules/git-commit.md rule file. Instead, it uses a default Angular Conventional Commits style (e.g., fix(cache): description) rather than my specified format with [what], [why], [how] sections.
Solution
The Qoder commit message generator should read and apply the custom rules defined in .qoder/rules/git-commit.md (project-level) or ~/.qoder/rules/git-commit.md (user-level). When a rule with trigger: always_on exists for commit message generation, the output should strictly follow the format specified in that rule, including:
Type prefix format (e.g., fix: instead of fix(scope)
Required sections ([what], [why], [how])
Language preference (Chinese vs English)
Use Case
Every time a developer stages files and clicks the Qoder auto-generate button to create a commit message, they expect the output to match their team’s commit conventions defined in the rule file. This ensures consistent commit history across the project without manually formatting each message.
Priority
Medium - Important improvement
Additional Info
Rule file location: D:\code\itds\mywork.qoder\rules\git-commit.md
Rule has trigger: always_on set but is not being applied
User skill also created at: C:\Users\cofin.qoder\skills\git-commit\SKILL.md
Current output format: fix(scope): description
Expected format:
fix: description
[what]
[why]
[how]
