feat: add commit message generation by markijbema · Pull Request #327 · Kilo-Org/kilo

markijbema · 2026-02-16T11:08:18Z

What

AI-powered commit message generation using Conventional Commits format. Uses small_model from the configured provider — no user model selection needed.

markijbema · 2026-02-16T15:42:13Z

packages/kilo-vscode/src/services/cli-backend/http-client.ts

  private readonly baseUrl: string
  private readonly authHeader: string
-  private readonly authUsername = "opencode"
+  private readonly authUsername = "kilo"


not sure why this broke, but it seems like this was changed in the backend breaking the vscode extension.

kilo-code-bot · 2026-02-16T17:04:31Z

packages/kilo-vscode/src/services/commit-message/index.ts

+  connectionService: KiloConnectionService,
+): vscode.Disposable[] {
+  const command = vscode.commands.registerCommand("kilo-code.new.generateCommitMessage", async () => {
+    const extension = vscode.extensions.getExtension<GitExtensionExports>("vscode.git")


SUGGESTION: Ensure the built-in Git extension is activated before accessing exports

vscode.extensions.getExtension('vscode.git') can return an extension object with exports undefined until it’s activated. Consider await extension.activate() before calling extension.exports.getAPI(1) to avoid incorrectly reporting "No Git repository found".

kilo-code-bot · 2026-02-16T17:04:31Z

packages/kilo-vscode/src/services/commit-message/index.ts

+      return
+    }
+
+    const client = connectionService.getHttpClient()


CRITICAL: connectionService.getHttpClient() appears to throw, so this null-check won’t work

packages/kilo-vscode/src/services/cli-backend/connection-service.ts defines getHttpClient(): HttpClient and throws when not connected. This line will throw before reaching the if (!client) branch, so the command will likely fail without showing "Kilo backend is not connected".

Consider wrapping this call in a try/catch (or adding a non-throwing accessor) so the user gets the intended error message.

kilo-code-bot · 2026-02-16T17:04:31Z

packages/opencode/src/cli/cmd/commit.ts

+        type: "boolean",
+        default: false,
+      })
+      .option("staged-only", {


WARNING: --staged-only option is defined but not used

The command builder defines staged-only (default true), but the handler always calls generateCommitMessage({ path: process.cwd() }) without using args['staged-only']. This will surprise users and makes the option misleading.

Either wire this flag through to the underlying git-context selection logic, or remove the option until it’s supported.

kilo-code-bot · 2026-02-16T17:04:31Z

packages/opencode/src/commit-message/git-context.ts

+function parseNameStatus(output: string): Array<{ status: string; path: string }> {
+  if (!output) return []
+  return output.split("\n").map((line) => {
+    const [status, ...rest] = line.split("\t")


WARNING: Rename entries from git diff --name-status are not parsed correctly

For rename status lines (e.g. R100 old.ts new.ts), rest.join('\t') produces a combined string like old.ts new.ts. Downstream, this entry.path is treated as a single path (lock-file filtering, selectedFiles filtering, and git diff ... -- entry.path), which will break for renames.

Consider parsing rename lines into a structured shape (old/new), and using the new path for .path (and/or storing both).

kilo-code-bot · 2026-02-16T17:04:31Z

packages/opencode/src/commit-message/git-context.ts

+    })
+}
+
+function mapStatus(code: string): FileChange["status"] {


SUGGESTION: FileChange['status'] includes untracked but it’s never produced

mapStatus() maps ?? / ? to added, while FileChange['status'] allows untracked. If untracked is intentionally modeled, consider returning untracked for ?? and adjusting handling; otherwise consider removing untracked from the union to avoid confusion.

packages/opencode/src/server/routes/commit-message.ts

kilo-code-bot · 2026-02-16T17:04:43Z

Code Review Summary

Status: 3 Issues Found | Recommendation: Address before merge

Overview

Severity	Count
CRITICAL	2
WARNING	1
SUGGESTION	0

Fix these issues in Kilo Cloud

Issue Details (click to expand)

CRITICAL

File	Line	Issue
`packages/opencode/src/commit-message/git-context.ts`	137	`git()` trims leading whitespace via `trimEnd()` only, but `parsePorcelain()` relies on the first 2 characters being the XY status columns — `trimEnd()` doesn't affect leading chars, however `stdout.toString()` may still lose data if `Bun.spawnSync` truncates. More critically, `git status --porcelain` output has a fixed-width format where the first char is the index status and the second is the worktree status; `xy.trim()` on line 163 collapses `" M"` → `"M"`, losing the distinction between staged and unstaged changes.
`packages/kilo-vscode/src/services/commit-message/index.ts`	63	Possible runtime error if `getHttpClient()` returns `undefined`/`null` instead of throwing — `client.generateCommitMessage(...)` would fail with an unhelpful error. The null check on line 50 mitigates this, but the `catch` block on line 46 is empty-ish (only shows error message, doesn't log the original error).

WARNING

File	Line	Issue
`packages/opencode/src/commit-message/generate.ts`	168	`new AbortController().signal` creates an orphaned controller that can never be aborted. If the HTTP client disconnects, the LLM stream continues running to completion, wasting tokens and server resources. Consider threading an `AbortSignal` from the request context.

Other Observations (not in diff)

Issues found in unchanged code that cannot receive inline comments:

File	Line	Issue
(none)	(n/a)	(n/a)

Files Reviewed (13 files)

packages/kilo-vscode/package.json - 0 issues
packages/kilo-vscode/src/extension.ts - 0 issues
packages/kilo-vscode/src/services/cli-backend/http-client.ts - 0 issues
packages/kilo-vscode/src/services/commit-message/__tests__/index.spec.ts - 0 issues
packages/kilo-vscode/src/services/commit-message/index.ts - 1 issue
packages/opencode/src/commit-message/__tests__/generate.test.ts - 0 issues
packages/opencode/src/commit-message/__tests__/git-context.test.ts - 0 issues
packages/opencode/src/commit-message/generate.ts - 1 issue
packages/opencode/src/commit-message/git-context.ts - 1 issue
packages/opencode/src/commit-message/index.ts - 0 issues
packages/opencode/src/commit-message/types.ts - 0 issues
packages/opencode/src/server/routes/commit-message.ts - 0 issues
packages/opencode/src/server/server.ts - 0 issues

kilo-code-bot · 2026-02-16T17:30:46Z

packages/kilo-vscode/src/services/commit-message/__tests__/index.spec.ts

+    })
+
+    it("shows error when no git repository is found", async () => {
+      vi.mocked(vscode.extensions.getExtension).mockReturnValue({


WARNING: Mocked vscode.git extension is missing isActive/activate, which can cause the command callback to throw

registerCommitMessageService() now checks if (!extension.isActive) await extension.activate(). In this test, the mocked extension object only provides exports, so extension.activate will be undefined and the callback will throw before reaching the "No Git repository found" branch.

Add isActive: true (or activate: vi.fn().mockResolvedValue(undefined) + isActive: false) to the mocked extension return values so the test exercises the intended path.

kilo-code-bot · 2026-02-16T17:30:46Z

packages/kilo-vscode/src/services/commit-message/__tests__/index.spec.ts

+          }),
+        },
+      } as any)
+      vi.mocked(mockConnectionService.getHttpClient as any).mockReturnValue(null)


WARNING: Test setup implies getHttpClient() returns null, but the production code assumes it throws (and never null-checks)

This test does mockReturnValue(null) and expects an error toast, but registerCommitMessageService() only handles the disconnected case via try/catch and then calls client.generateCommitMessage(...) unconditionally. If getHttpClient() ever returned null without throwing, this would become a runtime error instead of a user-facing message.

Either (a) update the test to mockImplementation(() => { throw new Error('...') }) to match the connection service contract, or (b) add an explicit if (!client) guard in the command implementation.

kilo-code-bot · 2026-02-16T17:30:46Z

packages/kilo-vscode/src/services/commit-message/index.ts

+      return
+    }
+
+    const path = folder.uri.fsPath


SUGGESTION: Use the git repository root path instead of the first workspace folder

When VS Code has multiple workspace folders (or the repo is not the first folder), using workspaceFolders[0] can generate a commit message for the wrong directory. Since you already have repository.rootUri, using that is more precise.

Suggested change

const path = folder.uri.fsPath

const path = repository.rootUri.fsPath

kilo-code-bot · 2026-02-16T18:18:32Z

packages/opencode/src/commit-message/git-context.ts

+    stdout: "pipe",
+    stderr: "pipe",
+  })
+  return result.stdout.toString().trim()


CRITICAL: git() trims leading whitespace, which can corrupt git status --porcelain parsing

Using packages/opencode/src/commit-message/git-context.ts:137, .trim() can remove the leading space of the first porcelain line (e.g. " M file"), shifting the fixed-column layout that parsePorcelain() relies on (slice(0,2) / slice(3)). This can drop the first character of the filepath (and then subsequent git diff -- <path> calls target the wrong file).

Suggested change

return result.stdout.toString().trim()

return result.stdout.toString().trimEnd()

kilo-code-bot · 2026-02-16T18:18:32Z

packages/kilo-vscode/src/services/commit-message/index.ts

+      .withProgress(
+        { location: vscode.ProgressLocation.SourceControl, title: "Generating commit message..." },
+        async () => {
+          const message = await client.generateCommitMessage(path, undefined, previousMessage)


CRITICAL: Possible runtime error if getHttpClient() returns undefined/null instead of throwing

packages/kilo-vscode/src/services/commit-message/index.ts:65 calls client.generateCommitMessage(...), but client is declared as HttpClient | undefined and the code only handles the throwing case. If connectionService.getHttpClient() returns undefined/null when disconnected, this will throw and show a generic failure message. Consider explicitly checking client after the call and returning early with a targeted error message.

vercel · 2026-02-19T09:05:52Z

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
kilo-ui-storybook	Ready	Preview, Comment	Feb 19, 2026 11:41am

… guidance

…stems

The mockGitContext variable was declared without a type annotation, causing TypeScript to infer a narrow type from the initial assignment (status: "modified"). This made reassignment with status: "added" fail with TS2322. Adding the GitContext type allows all valid status values.

- Use trimEnd() instead of trim() in git() to preserve leading whitespace in porcelain output (fixes status parsing for ' M file' lines) - Remove unused 'untracked' from FileChange status union - Use repository.rootUri.fsPath instead of workspaceFolders[0] - Add explicit null-check for client after try/catch - Fix test mocks: add isActive/activate, use mockImplementation to throw, fix expected error message to match production code

kilo-code-bot · 2026-02-19T15:31:30Z

packages/opencode/src/commit-message/generate.ts

+        content: userMessage,
+      },
+    ],
+    abort: new AbortController().signal,


WARNING: The AbortController created here is immediately orphaned — no reference is kept, so the LLM stream can never be cancelled.

If the HTTP client disconnects (e.g. user cancels in VS Code), this stream will continue running to completion, consuming LLM tokens and server resources.

Consider accepting an AbortSignal from the Hono request context (e.g. c.req.raw.signal) and threading it through to generateCommitMessage, so the stream is cancelled when the client disconnects.

github-actions bot added the contributor label Feb 16, 2026

markijbema commented Feb 16, 2026

View reviewed changes

markijbema marked this pull request as ready for review February 16, 2026 17:00

markijbema requested review from catrielmuller and marius-kilocode February 16, 2026 17:00

kilo-code-bot bot reviewed Feb 16, 2026

View reviewed changes

This comment has been minimized.

Sign in to view

kilo-code-bot bot reviewed Feb 16, 2026

View reviewed changes

markijbema marked this pull request as draft February 17, 2026 10:18

markijbema force-pushed the mark/feat-commit-message-generation branch from 49a572f to b6a4668 Compare February 19, 2026 09:05

vercel bot deployed to Preview February 19, 2026 09:06 View deployment

vercel bot temporarily deployed to Preview February 19, 2026 09:15 Inactive

markijbema force-pushed the mark/feat-commit-message-generation branch from a58ee63 to fbdaa6a Compare February 19, 2026 10:09

vercel bot deployed to Preview – kilo-ui-storybook February 19, 2026 10:10 View deployment

vercel bot deployed to Preview – kilo-ui-storybook February 19, 2026 11:41 View deployment

markijbema requested review from chrarnoldus and iscekic and removed request for catrielmuller and marius-kilocode February 19, 2026 15:24

markijbema marked this pull request as ready for review February 19, 2026 15:24

markijbema added 7 commits February 19, 2026 16:26

feat: add commit message generation feature

a7cc035

fix: update Basic auth username from opencode to kilo

0c21308

fix: use Kilo logo icon for commit message SCM button

5612075

chore: remove commit message implementation plans from PR

764f7b2

fix: enhance commit message prompt with detailed Conventional Commits…

2ecb523

… guidance

feat: add regenerate-different-message support

158f87f

fix: expand lock file exclusion list to 80+ patterns across 25+ ecosy…

51329c4

…stems

markijbema added 7 commits February 19, 2026 16:26

fix: handle getHttpClient() throw in commit message service

bc24a20

fix: remove unused --staged-only CLI option

e906306

fix: parse git rename entries correctly in git-context

c071a6c

fix: activate Git extension before accessing exports

70df946

refactor: remove commit message CLI command, keep core logic for clients

9faf4c3

markijbema force-pushed the mark/feat-commit-message-generation branch from 7674375 to bc27d89 Compare February 19, 2026 15:26

kilo-code-bot bot reviewed Feb 19, 2026

View reviewed changes

chrarnoldus approved these changes Feb 19, 2026

View reviewed changes

markijbema merged commit 80482b1 into dev Feb 19, 2026
7 checks passed

markijbema deleted the mark/feat-commit-message-generation branch February 19, 2026 15:38

markijbema mentioned this pull request Feb 23, 2026

[FEATURE]: Commit Message Generation Kilo-Org/kilocode#6065

Closed

1 task

	const path = folder.uri.fsPath
	const path = repository.rootUri.fsPath

	return result.stdout.toString().trim()
	return result.stdout.toString().trimEnd()

Conversation

markijbema commented Feb 16, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

What

Uh oh!

markijbema Feb 16, 2026

Choose a reason for hiding this comment

Uh oh!

kilo-code-bot bot Feb 16, 2026

Choose a reason for hiding this comment

Uh oh!

kilo-code-bot bot Feb 16, 2026

Choose a reason for hiding this comment

Uh oh!

kilo-code-bot bot Feb 16, 2026

Choose a reason for hiding this comment

Uh oh!

kilo-code-bot bot Feb 16, 2026

Choose a reason for hiding this comment

Uh oh!

kilo-code-bot bot Feb 16, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

kilo-code-bot bot commented Feb 16, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Code Review Summary

Overview

CRITICAL

WARNING

Uh oh!

kilo-code-bot bot Feb 16, 2026

Choose a reason for hiding this comment

Uh oh!

kilo-code-bot bot Feb 16, 2026

Choose a reason for hiding this comment

Uh oh!

kilo-code-bot bot Feb 16, 2026

Choose a reason for hiding this comment

Uh oh!

This comment has been minimized.

kilo-code-bot bot Feb 16, 2026

Choose a reason for hiding this comment

Uh oh!

kilo-code-bot bot Feb 16, 2026

Choose a reason for hiding this comment

Uh oh!

vercel bot commented Feb 19, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

kilo-code-bot bot Feb 19, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

markijbema commented Feb 16, 2026 •

edited

Loading

kilo-code-bot bot commented Feb 16, 2026 •

edited

Loading

vercel bot commented Feb 19, 2026 •

edited

Loading