feat(git): enforce Conventional Commits format in commit message prompt by pedrokpp · Pull Request #2123 · pingdotgg/t3code

pedrokpp · 2026-04-17T13:16:50Z

What changed

One rule in buildCommitMessagePrompt (apps/server/src/git/Prompts.ts):

Before:

- subject must be imperative, <= 72 chars, and no trailing period

After:

- 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, <= 72 chars total, no trailing period

Why it should exist

t3code already enforces a naming convention for branches via sanitizeFeatureBranchName (packages/shared/src/git.ts), which hard-codes the feature/ gitflow prefix on every generated branch. The same intent — consistent, predictable output — applies to commit messages.

Right now the prompt produces freeform imperative subjects with no structure. Conventional Commits gives changelogs, tooling, and contributors a machine-readable signal without adding friction. It's the natural complement to the existing branch convention.

Closes#656.

Testing

Generate a commit message through the UI with staged changes and verify the output follows type(scope): description format.

Note

Low Risk
Prompt-only change to text generation; no auth, git execution, or schema changes beyond LLM instructions.

Overview
AI-generated commit subjects from buildCommitMessagePrompt are now instructed to use Conventional Commits (type(scope): description) instead of a free-form imperative line.

The prompt replaces a single subject rule with explicit constraints: allowed types (feat, fix, docs, style, refactor, test, chore), optional scope, imperative description with no trailing period, and a ≤72 character full subject line. JSON shape and downstream handling (e.g. sanitizeCommitSubject in Claude/Codex/Cursor text generation) are unchanged—only what the model is told to produce shifts.

^{Reviewed by Cursor Bugbot for commit b8faa63. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Enforce Conventional Commits format in `buildCommitMessagePrompt`

Updates the prompt rules in Prompts.ts to require subjects in type(scope): description format. The allowed types are feat|fix|docs|style|refactor|test|chore, scope is optional, the description must be imperative with no trailing period, and the full subject line must be ≤72 characters. Behavioral Change: any AI-generated commit messages produced via this prompt will now follow Conventional Commits structure rather than free-form imperative style.

^{Macroscope summarized b8faa63.}

coderabbitai · 2026-04-17T13:20:06Z

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 0d82ba1a-18a8-48f9-9822-5a37db9716cd

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands.}

pedrokpp · 2026-04-17T13:24:45Z

Ran into this while using t3code — generated commit messages had no consistent structure, making history hard to scan and breaking tooling that expects a predictable format.

A few other attempts exist for related problems:

feat(server): infer commit and PR title style from repo history #1112 — infers style from repo history (open, XL)
Add customizable commit message instructions in settings #1023 — customizable commit instructions via settings (closed)
✨ add gitmoji-aware commit message generation #658 — gitmoji-aware generation (open, XXL)

Those are larger in scope. This PR does one thing: adds Conventional Commits rules to the prompt, consistent with the feature/ branch naming already enforced by sanitizeFeatureBranchName. Small, focused, no new surface area — tried to stay within the contributing guidelines.

pedrokpp · 2026-04-17T13:41:26Z

This is intentionally minimal — a temporary fix until there's a more robust solution for customizable commit conventions.

A more flexible approach could be delegating style guidelines to the user's AGENTS.md, letting each project define its own commit conventions rather than hardcoding Conventional Commits. That said, happy to keep this simple and wait for feedback on the direction you'd prefer.

macroscopeapp · 2026-04-17T13:54:17Z

Approvability

Verdict: Approved

This change modifies AI prompt instructions to enforce Conventional Commits format for generated commit messages. It's a low-risk, self-contained change to documentation/prompt text with no runtime behavior impact beyond the format of generated commit messages.

^{You can customize Macroscope's approvability policy. Learn more.}

fazulk · 2026-04-17T19:08:17Z

This is like the one thing preventing me from using t3 as a daily driver. please merge!

Replaces the loose subject rule with explicit Conventional Commits format (type(scope): description), consistent with the existing gitflow branch naming enforced by sanitizeFeatureBranchName.

cursor

Cursor Bugbot has reviewed your changes using high effort and found 2 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want fixes drafted automatically? Bugbot Autofix can create code changes for findings. A team admin can enable Autofix in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit b8faa63. Configure here.}

cursor · 2026-07-17T20:54:42Z

+ "- 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",


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.
^{Reviewed by Cursor Bugbot for commit b8faa63. Configure here.}

cursor · 2026-07-17T20:54:42Z

- "- 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",


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.
^{Reviewed by Cursor Bugbot for commit b8faa63. Configure here.}

t3-code · 2026-08-04T14:42:18Z

Closing as superseded by #4204, which added configurable commit message styles rather than hardcoding Conventional Commits: #4204

pedrokpp · 2026-04-17T13:16:50Z

What changed

One rule in buildCommitMessagePrompt (apps/server/src/git/Prompts.ts):

Before:

- subject must be imperative, <= 72 chars, and no trailing period

After:

- 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, <= 72 chars total, no trailing period

Why it should exist

t3code already enforces a naming convention for branches via sanitizeFeatureBranchName (packages/shared/src/git.ts), which hard-codes the feature/ gitflow prefix on every generated branch. The same intent — consistent, predictable output — applies to commit messages.

Right now the prompt produces freeform imperative subjects with no structure. Conventional Commits gives changelogs, tooling, and contributors a machine-readable signal without adding friction. It's the natural complement to the existing branch convention.

Closes#656.

Testing

Generate a commit message through the UI with staged changes and verify the output follows type(scope): description format.

Note

Low Risk
Prompt-only change to text generation; no auth, git execution, or schema changes beyond LLM instructions.

Overview
AI-generated commit subjects from buildCommitMessagePrompt are now instructed to use Conventional Commits (type(scope): description) instead of a free-form imperative line.

The prompt replaces a single subject rule with explicit constraints: allowed types (feat, fix, docs, style, refactor, test, chore), optional scope, imperative description with no trailing period, and a ≤72 character full subject line. JSON shape and downstream handling (e.g. sanitizeCommitSubject in Claude/Codex/Cursor text generation) are unchanged—only what the model is told to produce shifts.

^{Reviewed by Cursor Bugbot for commit b8faa63. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Enforce Conventional Commits format in `buildCommitMessagePrompt`

Updates the prompt rules in Prompts.ts to require subjects in type(scope): description format. The allowed types are feat|fix|docs|style|refactor|test|chore, scope is optional, the description must be imperative with no trailing period, and the full subject line must be ≤72 characters. Behavioral Change: any AI-generated commit messages produced via this prompt will now follow Conventional Commits structure rather than free-form imperative style.

^{Macroscope summarized b8faa63.}

coderabbitai · 2026-04-17T13:20:06Z

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 0d82ba1a-18a8-48f9-9822-5a37db9716cd

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands.}

pedrokpp · 2026-04-17T13:24:45Z

Ran into this while using t3code — generated commit messages had no consistent structure, making history hard to scan and breaking tooling that expects a predictable format.

A few other attempts exist for related problems:

feat(server): infer commit and PR title style from repo history #1112 — infers style from repo history (open, XL)
Add customizable commit message instructions in settings #1023 — customizable commit instructions via settings (closed)
✨ add gitmoji-aware commit message generation #658 — gitmoji-aware generation (open, XXL)

Those are larger in scope. This PR does one thing: adds Conventional Commits rules to the prompt, consistent with the feature/ branch naming already enforced by sanitizeFeatureBranchName. Small, focused, no new surface area — tried to stay within the contributing guidelines.

pedrokpp · 2026-04-17T13:41:26Z

This is intentionally minimal — a temporary fix until there's a more robust solution for customizable commit conventions.

A more flexible approach could be delegating style guidelines to the user's AGENTS.md, letting each project define its own commit conventions rather than hardcoding Conventional Commits. That said, happy to keep this simple and wait for feedback on the direction you'd prefer.

macroscopeapp · 2026-04-17T13:54:17Z

Approvability

Verdict: Approved

This change modifies AI prompt instructions to enforce Conventional Commits format for generated commit messages. It's a low-risk, self-contained change to documentation/prompt text with no runtime behavior impact beyond the format of generated commit messages.

^{You can customize Macroscope's approvability policy. Learn more.}

fazulk · 2026-04-17T19:08:17Z

This is like the one thing preventing me from using t3 as a daily driver. please merge!

Replaces the loose subject rule with explicit Conventional Commits format (type(scope): description), consistent with the existing gitflow branch naming enforced by sanitizeFeatureBranchName.

cursor

Cursor Bugbot has reviewed your changes using high effort and found 2 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want fixes drafted automatically? Bugbot Autofix can create code changes for findings. A team admin can enable Autofix in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit b8faa63. Configure here.}

cursor · 2026-07-17T20:54:42Z

+ "- 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",


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.
^{Reviewed by Cursor Bugbot for commit b8faa63. Configure here.}

cursor · 2026-07-17T20:54:42Z

- "- 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",


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.
^{Reviewed by Cursor Bugbot for commit b8faa63. Configure here.}

t3-code · 2026-08-04T14:42:18Z

Closing as superseded by #4204, which added configurable commit message styles rather than hardcoding Conventional Commits: #4204

pedrokpp · 2026-04-17T13:16:50Z

What changed

One rule in buildCommitMessagePrompt (apps/server/src/git/Prompts.ts):

Before:

- subject must be imperative, <= 72 chars, and no trailing period

After:

- 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, <= 72 chars total, no trailing period

Why it should exist

t3code already enforces a naming convention for branches via sanitizeFeatureBranchName (packages/shared/src/git.ts), which hard-codes the feature/ gitflow prefix on every generated branch. The same intent — consistent, predictable output — applies to commit messages.

Right now the prompt produces freeform imperative subjects with no structure. Conventional Commits gives changelogs, tooling, and contributors a machine-readable signal without adding friction. It's the natural complement to the existing branch convention.

Closes#656.

Testing

Generate a commit message through the UI with staged changes and verify the output follows type(scope): description format.

Note

Low Risk
Prompt-only change to text generation; no auth, git execution, or schema changes beyond LLM instructions.

Overview
AI-generated commit subjects from buildCommitMessagePrompt are now instructed to use Conventional Commits (type(scope): description) instead of a free-form imperative line.

The prompt replaces a single subject rule with explicit constraints: allowed types (feat, fix, docs, style, refactor, test, chore), optional scope, imperative description with no trailing period, and a ≤72 character full subject line. JSON shape and downstream handling (e.g. sanitizeCommitSubject in Claude/Codex/Cursor text generation) are unchanged—only what the model is told to produce shifts.

^{Reviewed by Cursor Bugbot for commit b8faa63. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Enforce Conventional Commits format in `buildCommitMessagePrompt`

Updates the prompt rules in Prompts.ts to require subjects in type(scope): description format. The allowed types are feat|fix|docs|style|refactor|test|chore, scope is optional, the description must be imperative with no trailing period, and the full subject line must be ≤72 characters. Behavioral Change: any AI-generated commit messages produced via this prompt will now follow Conventional Commits structure rather than free-form imperative style.

^{Macroscope summarized b8faa63.}

coderabbitai · 2026-04-17T13:20:06Z

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 0d82ba1a-18a8-48f9-9822-5a37db9716cd

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands.}

pedrokpp · 2026-04-17T13:24:45Z

Ran into this while using t3code — generated commit messages had no consistent structure, making history hard to scan and breaking tooling that expects a predictable format.

A few other attempts exist for related problems:

feat(server): infer commit and PR title style from repo history #1112 — infers style from repo history (open, XL)
Add customizable commit message instructions in settings #1023 — customizable commit instructions via settings (closed)
✨ add gitmoji-aware commit message generation #658 — gitmoji-aware generation (open, XXL)

Those are larger in scope. This PR does one thing: adds Conventional Commits rules to the prompt, consistent with the feature/ branch naming already enforced by sanitizeFeatureBranchName. Small, focused, no new surface area — tried to stay within the contributing guidelines.

pedrokpp · 2026-04-17T13:41:26Z

This is intentionally minimal — a temporary fix until there's a more robust solution for customizable commit conventions.

A more flexible approach could be delegating style guidelines to the user's AGENTS.md, letting each project define its own commit conventions rather than hardcoding Conventional Commits. That said, happy to keep this simple and wait for feedback on the direction you'd prefer.

macroscopeapp · 2026-04-17T13:54:17Z

Approvability

Verdict: Approved

This change modifies AI prompt instructions to enforce Conventional Commits format for generated commit messages. It's a low-risk, self-contained change to documentation/prompt text with no runtime behavior impact beyond the format of generated commit messages.

^{You can customize Macroscope's approvability policy. Learn more.}

fazulk · 2026-04-17T19:08:17Z

This is like the one thing preventing me from using t3 as a daily driver. please merge!

Replaces the loose subject rule with explicit Conventional Commits format (type(scope): description), consistent with the existing gitflow branch naming enforced by sanitizeFeatureBranchName.

cursor

Cursor Bugbot has reviewed your changes using high effort and found 2 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want fixes drafted automatically? Bugbot Autofix can create code changes for findings. A team admin can enable Autofix in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit b8faa63. Configure here.}

cursor · 2026-07-17T20:54:42Z

+ "- 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",


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.
^{Reviewed by Cursor Bugbot for commit b8faa63. Configure here.}

cursor · 2026-07-17T20:54:42Z

- "- 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",


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.
^{Reviewed by Cursor Bugbot for commit b8faa63. Configure here.}

t3-code · 2026-08-04T14:42:18Z

Closing as superseded by #4204, which added configurable commit message styles rather than hardcoding Conventional Commits: #4204

pedrokpp · 2026-04-17T13:16:50Z

What changed

One rule in buildCommitMessagePrompt (apps/server/src/git/Prompts.ts):

Before:

- subject must be imperative, <= 72 chars, and no trailing period

After:

- 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, <= 72 chars total, no trailing period

Why it should exist

t3code already enforces a naming convention for branches via sanitizeFeatureBranchName (packages/shared/src/git.ts), which hard-codes the feature/ gitflow prefix on every generated branch. The same intent — consistent, predictable output — applies to commit messages.

Right now the prompt produces freeform imperative subjects with no structure. Conventional Commits gives changelogs, tooling, and contributors a machine-readable signal without adding friction. It's the natural complement to the existing branch convention.

Closes#656.

Testing

Generate a commit message through the UI with staged changes and verify the output follows type(scope): description format.

Note

Low Risk
Prompt-only change to text generation; no auth, git execution, or schema changes beyond LLM instructions.

Overview
AI-generated commit subjects from buildCommitMessagePrompt are now instructed to use Conventional Commits (type(scope): description) instead of a free-form imperative line.

The prompt replaces a single subject rule with explicit constraints: allowed types (feat, fix, docs, style, refactor, test, chore), optional scope, imperative description with no trailing period, and a ≤72 character full subject line. JSON shape and downstream handling (e.g. sanitizeCommitSubject in Claude/Codex/Cursor text generation) are unchanged—only what the model is told to produce shifts.

^{Reviewed by Cursor Bugbot for commit b8faa63. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Enforce Conventional Commits format in `buildCommitMessagePrompt`

Updates the prompt rules in Prompts.ts to require subjects in type(scope): description format. The allowed types are feat|fix|docs|style|refactor|test|chore, scope is optional, the description must be imperative with no trailing period, and the full subject line must be ≤72 characters. Behavioral Change: any AI-generated commit messages produced via this prompt will now follow Conventional Commits structure rather than free-form imperative style.

^{Macroscope summarized b8faa63.}

coderabbitai · 2026-04-17T13:20:06Z

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 0d82ba1a-18a8-48f9-9822-5a37db9716cd

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands.}

pedrokpp · 2026-04-17T13:24:45Z

Ran into this while using t3code — generated commit messages had no consistent structure, making history hard to scan and breaking tooling that expects a predictable format.

A few other attempts exist for related problems:

feat(server): infer commit and PR title style from repo history #1112 — infers style from repo history (open, XL)
Add customizable commit message instructions in settings #1023 — customizable commit instructions via settings (closed)
✨ add gitmoji-aware commit message generation #658 — gitmoji-aware generation (open, XXL)

Those are larger in scope. This PR does one thing: adds Conventional Commits rules to the prompt, consistent with the feature/ branch naming already enforced by sanitizeFeatureBranchName. Small, focused, no new surface area — tried to stay within the contributing guidelines.

pedrokpp · 2026-04-17T13:41:26Z

This is intentionally minimal — a temporary fix until there's a more robust solution for customizable commit conventions.

A more flexible approach could be delegating style guidelines to the user's AGENTS.md, letting each project define its own commit conventions rather than hardcoding Conventional Commits. That said, happy to keep this simple and wait for feedback on the direction you'd prefer.

macroscopeapp · 2026-04-17T13:54:17Z

Approvability

Verdict: Approved

This change modifies AI prompt instructions to enforce Conventional Commits format for generated commit messages. It's a low-risk, self-contained change to documentation/prompt text with no runtime behavior impact beyond the format of generated commit messages.

^{You can customize Macroscope's approvability policy. Learn more.}

fazulk · 2026-04-17T19:08:17Z

This is like the one thing preventing me from using t3 as a daily driver. please merge!

Replaces the loose subject rule with explicit Conventional Commits format (type(scope): description), consistent with the existing gitflow branch naming enforced by sanitizeFeatureBranchName.

cursor

Cursor Bugbot has reviewed your changes using high effort and found 2 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want fixes drafted automatically? Bugbot Autofix can create code changes for findings. A team admin can enable Autofix in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit b8faa63. Configure here.}

cursor · 2026-07-17T20:54:42Z

+ "- 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",


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.
^{Reviewed by Cursor Bugbot for commit b8faa63. Configure here.}

cursor · 2026-07-17T20:54:42Z

- "- 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",


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.
^{Reviewed by Cursor Bugbot for commit b8faa63. Configure here.}

t3-code · 2026-08-04T14:42:18Z

Closing as superseded by #4204, which added configurable commit message styles rather than hardcoding Conventional Commits: #4204

pedrokpp · 2026-04-17T13:16:50Z

What changed

One rule in buildCommitMessagePrompt (apps/server/src/git/Prompts.ts):

Before:

- subject must be imperative, <= 72 chars, and no trailing period

After:

- 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, <= 72 chars total, no trailing period

Why it should exist

t3code already enforces a naming convention for branches via sanitizeFeatureBranchName (packages/shared/src/git.ts), which hard-codes the feature/ gitflow prefix on every generated branch. The same intent — consistent, predictable output — applies to commit messages.

Right now the prompt produces freeform imperative subjects with no structure. Conventional Commits gives changelogs, tooling, and contributors a machine-readable signal without adding friction. It's the natural complement to the existing branch convention.

Closes#656.

Testing

Generate a commit message through the UI with staged changes and verify the output follows type(scope): description format.

Note

Low Risk
Prompt-only change to text generation; no auth, git execution, or schema changes beyond LLM instructions.

Overview
AI-generated commit subjects from buildCommitMessagePrompt are now instructed to use Conventional Commits (type(scope): description) instead of a free-form imperative line.

The prompt replaces a single subject rule with explicit constraints: allowed types (feat, fix, docs, style, refactor, test, chore), optional scope, imperative description with no trailing period, and a ≤72 character full subject line. JSON shape and downstream handling (e.g. sanitizeCommitSubject in Claude/Codex/Cursor text generation) are unchanged—only what the model is told to produce shifts.

^{Reviewed by Cursor Bugbot for commit b8faa63. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Enforce Conventional Commits format in `buildCommitMessagePrompt`

Updates the prompt rules in Prompts.ts to require subjects in type(scope): description format. The allowed types are feat|fix|docs|style|refactor|test|chore, scope is optional, the description must be imperative with no trailing period, and the full subject line must be ≤72 characters. Behavioral Change: any AI-generated commit messages produced via this prompt will now follow Conventional Commits structure rather than free-form imperative style.

^{Macroscope summarized b8faa63.}

coderabbitai · 2026-04-17T13:20:06Z

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 0d82ba1a-18a8-48f9-9822-5a37db9716cd

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands.}

pedrokpp · 2026-04-17T13:24:45Z

Ran into this while using t3code — generated commit messages had no consistent structure, making history hard to scan and breaking tooling that expects a predictable format.

A few other attempts exist for related problems:

feat(server): infer commit and PR title style from repo history #1112 — infers style from repo history (open, XL)
Add customizable commit message instructions in settings #1023 — customizable commit instructions via settings (closed)
✨ add gitmoji-aware commit message generation #658 — gitmoji-aware generation (open, XXL)

Those are larger in scope. This PR does one thing: adds Conventional Commits rules to the prompt, consistent with the feature/ branch naming already enforced by sanitizeFeatureBranchName. Small, focused, no new surface area — tried to stay within the contributing guidelines.

pedrokpp · 2026-04-17T13:41:26Z

This is intentionally minimal — a temporary fix until there's a more robust solution for customizable commit conventions.

A more flexible approach could be delegating style guidelines to the user's AGENTS.md, letting each project define its own commit conventions rather than hardcoding Conventional Commits. That said, happy to keep this simple and wait for feedback on the direction you'd prefer.

macroscopeapp · 2026-04-17T13:54:17Z

Approvability

Verdict: Approved

This change modifies AI prompt instructions to enforce Conventional Commits format for generated commit messages. It's a low-risk, self-contained change to documentation/prompt text with no runtime behavior impact beyond the format of generated commit messages.

^{You can customize Macroscope's approvability policy. Learn more.}

fazulk · 2026-04-17T19:08:17Z

This is like the one thing preventing me from using t3 as a daily driver. please merge!

Replaces the loose subject rule with explicit Conventional Commits format (type(scope): description), consistent with the existing gitflow branch naming enforced by sanitizeFeatureBranchName.

cursor

Cursor Bugbot has reviewed your changes using high effort and found 2 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want fixes drafted automatically? Bugbot Autofix can create code changes for findings. A team admin can enable Autofix in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit b8faa63. Configure here.}

cursor · 2026-07-17T20:54:42Z

+ "- 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",


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.
^{Reviewed by Cursor Bugbot for commit b8faa63. Configure here.}

cursor · 2026-07-17T20:54:42Z

- "- 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",


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.
^{Reviewed by Cursor Bugbot for commit b8faa63. Configure here.}

t3-code · 2026-08-04T14:42:18Z

Closing as superseded by #4204, which added configurable commit message styles rather than hardcoding Conventional Commits: #4204

pedrokpp · 2026-04-17T13:16:50Z

What changed

One rule in buildCommitMessagePrompt (apps/server/src/git/Prompts.ts):

Before:

- subject must be imperative, <= 72 chars, and no trailing period

After:

- 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, <= 72 chars total, no trailing period

Why it should exist

t3code already enforces a naming convention for branches via sanitizeFeatureBranchName (packages/shared/src/git.ts), which hard-codes the feature/ gitflow prefix on every generated branch. The same intent — consistent, predictable output — applies to commit messages.

Right now the prompt produces freeform imperative subjects with no structure. Conventional Commits gives changelogs, tooling, and contributors a machine-readable signal without adding friction. It's the natural complement to the existing branch convention.

Closes#656.

Testing

Generate a commit message through the UI with staged changes and verify the output follows type(scope): description format.

Note

Low Risk
Prompt-only change to text generation; no auth, git execution, or schema changes beyond LLM instructions.

Overview
AI-generated commit subjects from buildCommitMessagePrompt are now instructed to use Conventional Commits (type(scope): description) instead of a free-form imperative line.

The prompt replaces a single subject rule with explicit constraints: allowed types (feat, fix, docs, style, refactor, test, chore), optional scope, imperative description with no trailing period, and a ≤72 character full subject line. JSON shape and downstream handling (e.g. sanitizeCommitSubject in Claude/Codex/Cursor text generation) are unchanged—only what the model is told to produce shifts.

^{Reviewed by Cursor Bugbot for commit b8faa63. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Enforce Conventional Commits format in `buildCommitMessagePrompt`

Updates the prompt rules in Prompts.ts to require subjects in type(scope): description format. The allowed types are feat|fix|docs|style|refactor|test|chore, scope is optional, the description must be imperative with no trailing period, and the full subject line must be ≤72 characters. Behavioral Change: any AI-generated commit messages produced via this prompt will now follow Conventional Commits structure rather than free-form imperative style.

^{Macroscope summarized b8faa63.}

coderabbitai · 2026-04-17T13:20:06Z

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 0d82ba1a-18a8-48f9-9822-5a37db9716cd

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands.}

pedrokpp · 2026-04-17T13:24:45Z

Ran into this while using t3code — generated commit messages had no consistent structure, making history hard to scan and breaking tooling that expects a predictable format.

A few other attempts exist for related problems:

feat(server): infer commit and PR title style from repo history #1112 — infers style from repo history (open, XL)
Add customizable commit message instructions in settings #1023 — customizable commit instructions via settings (closed)
✨ add gitmoji-aware commit message generation #658 — gitmoji-aware generation (open, XXL)

Those are larger in scope. This PR does one thing: adds Conventional Commits rules to the prompt, consistent with the feature/ branch naming already enforced by sanitizeFeatureBranchName. Small, focused, no new surface area — tried to stay within the contributing guidelines.

pedrokpp · 2026-04-17T13:41:26Z

This is intentionally minimal — a temporary fix until there's a more robust solution for customizable commit conventions.

A more flexible approach could be delegating style guidelines to the user's AGENTS.md, letting each project define its own commit conventions rather than hardcoding Conventional Commits. That said, happy to keep this simple and wait for feedback on the direction you'd prefer.

macroscopeapp · 2026-04-17T13:54:17Z

Approvability

Verdict: Approved

This change modifies AI prompt instructions to enforce Conventional Commits format for generated commit messages. It's a low-risk, self-contained change to documentation/prompt text with no runtime behavior impact beyond the format of generated commit messages.

^{You can customize Macroscope's approvability policy. Learn more.}

fazulk · 2026-04-17T19:08:17Z

This is like the one thing preventing me from using t3 as a daily driver. please merge!

Replaces the loose subject rule with explicit Conventional Commits format (type(scope): description), consistent with the existing gitflow branch naming enforced by sanitizeFeatureBranchName.

cursor

Cursor Bugbot has reviewed your changes using high effort and found 2 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want fixes drafted automatically? Bugbot Autofix can create code changes for findings. A team admin can enable Autofix in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit b8faa63. Configure here.}

cursor · 2026-07-17T20:54:42Z

+ "- 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",


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.
^{Reviewed by Cursor Bugbot for commit b8faa63. Configure here.}

cursor · 2026-07-17T20:54:42Z

- "- 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",


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.
^{Reviewed by Cursor Bugbot for commit b8faa63. Configure here.}

t3-code · 2026-08-04T14:42:18Z

Closing as superseded by #4204, which added configurable commit message styles rather than hardcoding Conventional Commits: #4204

pedrokpp · 2026-04-17T13:16:50Z

What changed

One rule in buildCommitMessagePrompt (apps/server/src/git/Prompts.ts):

Before:

- subject must be imperative, <= 72 chars, and no trailing period

After:

- 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, <= 72 chars total, no trailing period

Why it should exist

t3code already enforces a naming convention for branches via sanitizeFeatureBranchName (packages/shared/src/git.ts), which hard-codes the feature/ gitflow prefix on every generated branch. The same intent — consistent, predictable output — applies to commit messages.

Right now the prompt produces freeform imperative subjects with no structure. Conventional Commits gives changelogs, tooling, and contributors a machine-readable signal without adding friction. It's the natural complement to the existing branch convention.

Closes#656.

Testing

Generate a commit message through the UI with staged changes and verify the output follows type(scope): description format.

Note

Low Risk
Prompt-only change to text generation; no auth, git execution, or schema changes beyond LLM instructions.

Overview
AI-generated commit subjects from buildCommitMessagePrompt are now instructed to use Conventional Commits (type(scope): description) instead of a free-form imperative line.

The prompt replaces a single subject rule with explicit constraints: allowed types (feat, fix, docs, style, refactor, test, chore), optional scope, imperative description with no trailing period, and a ≤72 character full subject line. JSON shape and downstream handling (e.g. sanitizeCommitSubject in Claude/Codex/Cursor text generation) are unchanged—only what the model is told to produce shifts.

^{Reviewed by Cursor Bugbot for commit b8faa63. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Enforce Conventional Commits format in `buildCommitMessagePrompt`

Updates the prompt rules in Prompts.ts to require subjects in type(scope): description format. The allowed types are feat|fix|docs|style|refactor|test|chore, scope is optional, the description must be imperative with no trailing period, and the full subject line must be ≤72 characters. Behavioral Change: any AI-generated commit messages produced via this prompt will now follow Conventional Commits structure rather than free-form imperative style.

^{Macroscope summarized b8faa63.}

coderabbitai · 2026-04-17T13:20:06Z

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 0d82ba1a-18a8-48f9-9822-5a37db9716cd

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands.}

pedrokpp · 2026-04-17T13:24:45Z

Ran into this while using t3code — generated commit messages had no consistent structure, making history hard to scan and breaking tooling that expects a predictable format.

A few other attempts exist for related problems:

feat(server): infer commit and PR title style from repo history #1112 — infers style from repo history (open, XL)
Add customizable commit message instructions in settings #1023 — customizable commit instructions via settings (closed)
✨ add gitmoji-aware commit message generation #658 — gitmoji-aware generation (open, XXL)

Those are larger in scope. This PR does one thing: adds Conventional Commits rules to the prompt, consistent with the feature/ branch naming already enforced by sanitizeFeatureBranchName. Small, focused, no new surface area — tried to stay within the contributing guidelines.

pedrokpp · 2026-04-17T13:41:26Z

This is intentionally minimal — a temporary fix until there's a more robust solution for customizable commit conventions.

A more flexible approach could be delegating style guidelines to the user's AGENTS.md, letting each project define its own commit conventions rather than hardcoding Conventional Commits. That said, happy to keep this simple and wait for feedback on the direction you'd prefer.

macroscopeapp · 2026-04-17T13:54:17Z

Approvability

Verdict: Approved

This change modifies AI prompt instructions to enforce Conventional Commits format for generated commit messages. It's a low-risk, self-contained change to documentation/prompt text with no runtime behavior impact beyond the format of generated commit messages.

^{You can customize Macroscope's approvability policy. Learn more.}

fazulk · 2026-04-17T19:08:17Z

This is like the one thing preventing me from using t3 as a daily driver. please merge!

Replaces the loose subject rule with explicit Conventional Commits format (type(scope): description), consistent with the existing gitflow branch naming enforced by sanitizeFeatureBranchName.

cursor

Cursor Bugbot has reviewed your changes using high effort and found 2 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want fixes drafted automatically? Bugbot Autofix can create code changes for findings. A team admin can enable Autofix in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit b8faa63. Configure here.}

cursor · 2026-07-17T20:54:42Z

+ "- 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",


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.
^{Reviewed by Cursor Bugbot for commit b8faa63. Configure here.}

cursor · 2026-07-17T20:54:42Z

- "- 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",


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.
^{Reviewed by Cursor Bugbot for commit b8faa63. Configure here.}

t3-code · 2026-08-04T14:42:18Z

Closing as superseded by #4204, which added configurable commit message styles rather than hardcoding Conventional Commits: #4204

pedrokpp · 2026-04-17T13:16:50Z

What changed

One rule in buildCommitMessagePrompt (apps/server/src/git/Prompts.ts):

Before:

- subject must be imperative, <= 72 chars, and no trailing period

After:

- 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, <= 72 chars total, no trailing period

Why it should exist

t3code already enforces a naming convention for branches via sanitizeFeatureBranchName (packages/shared/src/git.ts), which hard-codes the feature/ gitflow prefix on every generated branch. The same intent — consistent, predictable output — applies to commit messages.

Right now the prompt produces freeform imperative subjects with no structure. Conventional Commits gives changelogs, tooling, and contributors a machine-readable signal without adding friction. It's the natural complement to the existing branch convention.

Closes#656.

Testing

Generate a commit message through the UI with staged changes and verify the output follows type(scope): description format.

Note

Low Risk
Prompt-only change to text generation; no auth, git execution, or schema changes beyond LLM instructions.

Overview
AI-generated commit subjects from buildCommitMessagePrompt are now instructed to use Conventional Commits (type(scope): description) instead of a free-form imperative line.

The prompt replaces a single subject rule with explicit constraints: allowed types (feat, fix, docs, style, refactor, test, chore), optional scope, imperative description with no trailing period, and a ≤72 character full subject line. JSON shape and downstream handling (e.g. sanitizeCommitSubject in Claude/Codex/Cursor text generation) are unchanged—only what the model is told to produce shifts.

^{Reviewed by Cursor Bugbot for commit b8faa63. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Enforce Conventional Commits format in `buildCommitMessagePrompt`

Updates the prompt rules in Prompts.ts to require subjects in type(scope): description format. The allowed types are feat|fix|docs|style|refactor|test|chore, scope is optional, the description must be imperative with no trailing period, and the full subject line must be ≤72 characters. Behavioral Change: any AI-generated commit messages produced via this prompt will now follow Conventional Commits structure rather than free-form imperative style.

^{Macroscope summarized b8faa63.}

coderabbitai · 2026-04-17T13:20:06Z

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 0d82ba1a-18a8-48f9-9822-5a37db9716cd

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands.}

pedrokpp · 2026-04-17T13:24:45Z

Ran into this while using t3code — generated commit messages had no consistent structure, making history hard to scan and breaking tooling that expects a predictable format.

A few other attempts exist for related problems:

feat(server): infer commit and PR title style from repo history #1112 — infers style from repo history (open, XL)
Add customizable commit message instructions in settings #1023 — customizable commit instructions via settings (closed)
✨ add gitmoji-aware commit message generation #658 — gitmoji-aware generation (open, XXL)

Those are larger in scope. This PR does one thing: adds Conventional Commits rules to the prompt, consistent with the feature/ branch naming already enforced by sanitizeFeatureBranchName. Small, focused, no new surface area — tried to stay within the contributing guidelines.

pedrokpp · 2026-04-17T13:41:26Z

This is intentionally minimal — a temporary fix until there's a more robust solution for customizable commit conventions.

A more flexible approach could be delegating style guidelines to the user's AGENTS.md, letting each project define its own commit conventions rather than hardcoding Conventional Commits. That said, happy to keep this simple and wait for feedback on the direction you'd prefer.

macroscopeapp · 2026-04-17T13:54:17Z

Approvability

Verdict: Approved

This change modifies AI prompt instructions to enforce Conventional Commits format for generated commit messages. It's a low-risk, self-contained change to documentation/prompt text with no runtime behavior impact beyond the format of generated commit messages.

^{You can customize Macroscope's approvability policy. Learn more.}

fazulk · 2026-04-17T19:08:17Z

This is like the one thing preventing me from using t3 as a daily driver. please merge!

Replaces the loose subject rule with explicit Conventional Commits format (type(scope): description), consistent with the existing gitflow branch naming enforced by sanitizeFeatureBranchName.

cursor

Cursor Bugbot has reviewed your changes using high effort and found 2 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want fixes drafted automatically? Bugbot Autofix can create code changes for findings. A team admin can enable Autofix in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit b8faa63. Configure here.}

cursor · 2026-07-17T20:54:42Z

+ "- 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",


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.
^{Reviewed by Cursor Bugbot for commit b8faa63. Configure here.}

cursor · 2026-07-17T20:54:42Z

- "- 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",


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.
^{Reviewed by Cursor Bugbot for commit b8faa63. Configure here.}

t3-code · 2026-08-04T14:42:18Z

Closing as superseded by #4204, which added configurable commit message styles rather than hardcoding Conventional Commits: #4204

github-actionsBot added size:XS 0-9 changed lines (additions + deletions). vouch:unvouched PR author is not yet trusted in the VOUCHED list. labels Apr 17, 2026

cursorBot reviewed Apr 17, 2026
View reviewed changes

Comment threadapps/server/src/git/Prompts.ts Outdated

macroscopeappBot approved these changes Apr 17, 2026
View reviewed changes

pedrokpp added 2 commits June 16, 2026 10:12

feat(git): enforce Conventional Commits in commit message prompt
042abea
Replaces the loose subject rule with explicit Conventional Commits format (type(scope): description), consistent with the existing gitflow branch naming enforced by sanitizeFeatureBranchName.

fix(git): clarify 72-char limit applies to full subject line
1dc45be

juliusmarminge force-pushed the feat/conventional-commits-prompt branch from dabc6e5 to 1dc45beCompare June 16, 2026 17:31

Merge branch 'main' into feat/conventional-commits-prompt
b8faa63

cursorBot reviewed Jul 17, 2026
View reviewed changes

t3-codeBot closed this Aug 4, 2026

github-actionsBot added size:XS 0-9 changed lines (additions + deletions). vouch:unvouched PR author is not yet trusted in the VOUCHED list. labels Apr 17, 2026

cursorBot reviewed Apr 17, 2026
View reviewed changes

Comment threadapps/server/src/git/Prompts.ts Outdated

macroscopeappBot approved these changes Apr 17, 2026
View reviewed changes

pedrokpp added 2 commits June 16, 2026 10:12

feat(git): enforce Conventional Commits in commit message prompt
042abea
Replaces the loose subject rule with explicit Conventional Commits format (type(scope): description), consistent with the existing gitflow branch naming enforced by sanitizeFeatureBranchName.

fix(git): clarify 72-char limit applies to full subject line
1dc45be

juliusmarminge force-pushed the feat/conventional-commits-prompt branch from dabc6e5 to 1dc45beCompare June 16, 2026 17:31

Merge branch 'main' into feat/conventional-commits-prompt
b8faa63

cursorBot reviewed Jul 17, 2026
View reviewed changes

t3-codeBot closed this Aug 4, 2026

github-actionsBot added size:XS 0-9 changed lines (additions + deletions). vouch:unvouched PR author is not yet trusted in the VOUCHED list. labels Apr 17, 2026

cursorBot reviewed Apr 17, 2026
View reviewed changes

Comment threadapps/server/src/git/Prompts.ts Outdated

macroscopeappBot approved these changes Apr 17, 2026
View reviewed changes

pedrokpp added 2 commits June 16, 2026 10:12

feat(git): enforce Conventional Commits in commit message prompt
042abea
Replaces the loose subject rule with explicit Conventional Commits format (type(scope): description), consistent with the existing gitflow branch naming enforced by sanitizeFeatureBranchName.

fix(git): clarify 72-char limit applies to full subject line
1dc45be

juliusmarminge force-pushed the feat/conventional-commits-prompt branch from dabc6e5 to 1dc45beCompare June 16, 2026 17:31

Merge branch 'main' into feat/conventional-commits-prompt
b8faa63

cursorBot reviewed Jul 17, 2026
View reviewed changes

t3-codeBot closed this Aug 4, 2026

github-actionsBot added size:XS 0-9 changed lines (additions + deletions). vouch:unvouched PR author is not yet trusted in the VOUCHED list. labels Apr 17, 2026

cursorBot reviewed Apr 17, 2026
View reviewed changes

Comment threadapps/server/src/git/Prompts.ts Outdated

macroscopeappBot approved these changes Apr 17, 2026
View reviewed changes

pedrokpp added 2 commits June 16, 2026 10:12

feat(git): enforce Conventional Commits in commit message prompt
042abea
Replaces the loose subject rule with explicit Conventional Commits format (type(scope): description), consistent with the existing gitflow branch naming enforced by sanitizeFeatureBranchName.

fix(git): clarify 72-char limit applies to full subject line
1dc45be

juliusmarminge force-pushed the feat/conventional-commits-prompt branch from dabc6e5 to 1dc45beCompare June 16, 2026 17:31

Merge branch 'main' into feat/conventional-commits-prompt
b8faa63

cursorBot reviewed Jul 17, 2026
View reviewed changes

t3-codeBot closed this Aug 4, 2026

github-actionsBot added size:XS 0-9 changed lines (additions + deletions). vouch:unvouched PR author is not yet trusted in the VOUCHED list. labels Apr 17, 2026

cursorBot reviewed Apr 17, 2026
View reviewed changes

Comment threadapps/server/src/git/Prompts.ts Outdated

macroscopeappBot approved these changes Apr 17, 2026
View reviewed changes

pedrokpp added 2 commits June 16, 2026 10:12

feat(git): enforce Conventional Commits in commit message prompt
042abea
Replaces the loose subject rule with explicit Conventional Commits format (type(scope): description), consistent with the existing gitflow branch naming enforced by sanitizeFeatureBranchName.

fix(git): clarify 72-char limit applies to full subject line
1dc45be

juliusmarminge force-pushed the feat/conventional-commits-prompt branch from dabc6e5 to 1dc45beCompare June 16, 2026 17:31

Merge branch 'main' into feat/conventional-commits-prompt
b8faa63

cursorBot reviewed Jul 17, 2026
View reviewed changes

t3-codeBot closed this Aug 4, 2026

github-actionsBot added size:XS 0-9 changed lines (additions + deletions). vouch:unvouched PR author is not yet trusted in the VOUCHED list. labels Apr 17, 2026

cursorBot reviewed Apr 17, 2026
View reviewed changes

Comment threadapps/server/src/git/Prompts.ts Outdated

macroscopeappBot approved these changes Apr 17, 2026
View reviewed changes

pedrokpp added 2 commits June 16, 2026 10:12

feat(git): enforce Conventional Commits in commit message prompt
042abea
Replaces the loose subject rule with explicit Conventional Commits format (type(scope): description), consistent with the existing gitflow branch naming enforced by sanitizeFeatureBranchName.

fix(git): clarify 72-char limit applies to full subject line
1dc45be

juliusmarminge force-pushed the feat/conventional-commits-prompt branch from dabc6e5 to 1dc45beCompare June 16, 2026 17:31

Merge branch 'main' into feat/conventional-commits-prompt
b8faa63

cursorBot reviewed Jul 17, 2026
View reviewed changes

t3-codeBot closed this Aug 4, 2026

github-actionsBot added size:XS 0-9 changed lines (additions + deletions). vouch:unvouched PR author is not yet trusted in the VOUCHED list. labels Apr 17, 2026

cursorBot reviewed Apr 17, 2026
View reviewed changes

Comment threadapps/server/src/git/Prompts.ts Outdated

macroscopeappBot approved these changes Apr 17, 2026
View reviewed changes

pedrokpp added 2 commits June 16, 2026 10:12

feat(git): enforce Conventional Commits in commit message prompt
042abea
Replaces the loose subject rule with explicit Conventional Commits format (type(scope): description), consistent with the existing gitflow branch naming enforced by sanitizeFeatureBranchName.

fix(git): clarify 72-char limit applies to full subject line
1dc45be

juliusmarminge force-pushed the feat/conventional-commits-prompt branch from dabc6e5 to 1dc45beCompare June 16, 2026 17:31

Merge branch 'main' into feat/conventional-commits-prompt
b8faa63

cursorBot reviewed Jul 17, 2026
View reviewed changes

t3-codeBot closed this Aug 4, 2026

github-actionsBot added size:XS 0-9 changed lines (additions + deletions). vouch:unvouched PR author is not yet trusted in the VOUCHED list. labels Apr 17, 2026

cursorBot reviewed Apr 17, 2026
View reviewed changes

Comment threadapps/server/src/git/Prompts.ts Outdated

macroscopeappBot approved these changes Apr 17, 2026
View reviewed changes

pedrokpp added 2 commits June 16, 2026 10:12

feat(git): enforce Conventional Commits in commit message prompt
042abea
Replaces the loose subject rule with explicit Conventional Commits format (type(scope): description), consistent with the existing gitflow branch naming enforced by sanitizeFeatureBranchName.

fix(git): clarify 72-char limit applies to full subject line
1dc45be

juliusmarminge force-pushed the feat/conventional-commits-prompt branch from dabc6e5 to 1dc45beCompare June 16, 2026 17:31

Merge branch 'main' into feat/conventional-commits-prompt
b8faa63

cursorBot reviewed Jul 17, 2026
View reviewed changes

t3-codeBot closed this Aug 4, 2026

Uh oh!

Conversation

pedrokpp commented Apr 17, 2026• edited by cursor BotLoading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

What changed

Why it should exist

Testing

Enforce Conventional Commits format in buildCommitMessagePrompt

Uh oh!

Uh oh!

coderabbitaiBot commented Apr 17, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Review skipped

Uh oh!

pedrokpp commented Apr 17, 2026

Uh oh!

pedrokpp commented Apr 17, 2026

Uh oh!

macroscopeappBot commented Apr 17, 2026

Approvability

Uh oh!

fazulk commented Apr 17, 2026

Uh oh!

cursorBot left a comment

Choose a reason for hiding this comment

Uh oh!

cursorBotJul 17, 2026

Choose a reason for hiding this comment

Sanitizer breaks new commit format

Uh oh!

cursorBotJul 17, 2026

Choose a reason for hiding this comment

Ambiguous optional scope format

Uh oh!

t3-codeBot commented Aug 4, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Uh oh!

Conversation

pedrokpp commented Apr 17, 2026• edited by cursor BotLoading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

What changed

Why it should exist

Testing

Enforce Conventional Commits format in buildCommitMessagePrompt

Uh oh!

Uh oh!

coderabbitaiBot commented Apr 17, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Review skipped

Uh oh!

pedrokpp commented Apr 17, 2026

Uh oh!

pedrokpp commented Apr 17, 2026

Uh oh!

macroscopeappBot commented Apr 17, 2026

Approvability

Uh oh!

fazulk commented Apr 17, 2026

Uh oh!

cursorBot left a comment

Choose a reason for hiding this comment

Uh oh!

cursorBotJul 17, 2026

Choose a reason for hiding this comment

Sanitizer breaks new commit format

Uh oh!

cursorBotJul 17, 2026

Choose a reason for hiding this comment

Ambiguous optional scope format

Uh oh!

t3-codeBot commented Aug 4, 2026

Uh oh!

pedrokpp commented Apr 17, 2026•
edited by cursor Bot
Loading

Enforce Conventional Commits format in `buildCommitMessagePrompt`

coderabbitaiBot commented Apr 17, 2026•
edited
Loading

pedrokpp commented Apr 17, 2026•
edited by cursor Bot
Loading

Enforce Conventional Commits format in `buildCommitMessagePrompt`

coderabbitaiBot commented Apr 17, 2026•
edited
Loading

pedrokpp commented Apr 17, 2026•
edited by cursor Bot
Loading

Enforce Conventional Commits format in `buildCommitMessagePrompt`

coderabbitaiBot commented Apr 17, 2026•
edited
Loading