Skip to content

feat(git): enforce Conventional Commits format in commit message prompt #2123

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
pedrokpp wants to merge 3 commits into
base: main
Choose a base branch
from
+4 −1
Open

feat(git): enforce Conventional Commits format in commit message prompt #2123

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
042abea
feat(git): enforce Conventional Commits in commit message prompt
pedrokpp Apr 17, 2026
1dc45be
fix(git): clarify 72-char limit applies to full subject line
pedrokpp Apr 17, 2026
b8faa63
Merge branch 'main' into feat/conventional-commits-prompt
juliusmarminge Jul 17, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion apps/server/src/textGeneration/TextGenerationPrompts.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,7 +38,10 @@ export function buildCommitMessagePrompt(input: CommitMessagePromptInput) {
? "Return a JSON object with keys: subject, body, branch."
: "Return a JSON object with keys: subject, body.",
"Rules:",
"- subject must be imperative, <= 72 chars, and no trailing period",
"- subject must follow Conventional Commits format: type(scope): description",
"- type must be one of: feat, fix, docs, style, refactor, test, chore",
"- scope is optional; description is imperative, no trailing period",

@cursor cursor Bot Jul 17, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Ambiguous optional scope format

Low Severity

The subject rule presents type(scope): description as the required shape while also saying scope is optional, without stating the no-scope form type: description. That can push models toward always inventing a scope or emitting empty parentheses, which is invalid Conventional Commits and weakens the consistency this change aims for.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit b8faa63. Configure here.

"- full subject line must be <= 72 chars",

@cursor cursor Bot Jul 17, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Sanitizer breaks new commit format

Low Severity

The prompt now requires Conventional Commits subjects, but sanitizeCommitSubject and sanitizeCommitMessage can still rewrite the model output into a non-conforming subject via hard slice(0, 72) truncation or the Update project files fallback, so the AI commit path does not actually guarantee the new format.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit b8faa63. Configure here.

"- body can be empty string or short bullet points",
...(wantsBranch
? ["- branch must be a short semantic git branch fragment for this change"]
Expand Down
Loading