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 2 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
2 commits
Select commit Hold shift + click to select a range
030b07b
feat(git): enforce Conventional Commits in commit message prompt
pedrokpp Apr 17, 2026
dabc6e5
fix(git): clarify 72-char limit applies to full subject line
pedrokpp Apr 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/git/Prompts.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,7 +31,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",
"- full subject line must be <= 72 chars",
"- 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