The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

src/data-loader.ts (1)

34-41: Validate the fallback path as well

getDefaultClaudePath now guarantees projects/ exists only when CLAUDE_CONFIG_DIR is set.
When the variable is not set we blindly return ~/.claude even if that directory (and its projects sub-dir) is missing.
load* functions later on use this path as cwd for tinyglobby; if it does not exist tinyglobby will throw, causing a less helpful stack trace.

-		return DEFAULT_CLAUDE_CODE_PATH;
+		const defaultProjectsPath = path.join(DEFAULT_CLAUDE_CODE_PATH, 'projects');
+		if (!isDirectorySync(defaultProjectsPath)) {
+			throw new Error(
+				`Claude data directory does not exist: ${defaultProjectsPath}. ` +
+				`Create it or set CLAUDE_CONFIG_DIR.`
+			);
+		}
+		return DEFAULT_CLAUDE_CODE_PATH;

src/data-loader.ts (1)

37-38: Super-fluous leading whitespace in error message

The template literal starts with a space, producing " Claude data directory…".
Trimming later removes line-breaks but keeps the leading space.

-			` Claude data directory does not exist: ${claudeCodeProjectsPath}. 
+			`Claude data directory does not exist: ${claudeCodeProjectsPath}. 

src/data-loader.test.ts (1)

103-110: Fix typo in test description

Minor typo: “dose” → “does”.

-test('throws an error when CLAUDE_CONFIG_DIR dose not have a "projects" directory', async () => {
+test('throws an error when CLAUDE_CONFIG_DIR does not have a "projects" directory', async () => {

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

src/data-loader.ts:34

• [nitpick] Consider adding a comment explaining why an empty CLAUDE_CONFIG_DIR results in returning DEFAULT_CLAUDE_CODE_PATH. This would improve clarity for future maintainers.

	if (envClaudeCodePath === '') {

src/data-loader.ts:1059

• [nitpick] Ensure the test fixture change from 'claude' to 'projects' aligns with the updated validation logic for the directory structure. Additional tests verifying the absence of the 'projects' subdirectory could further enhance coverage.

				projects: {},

src/data-loader.ts (1)

33-38: Still missing the early check that CLAUDE_CONFIG_DIR itself is a directory

The earlier review already pointed this out: if CLAUDE_CONFIG_DIR points to an existing file (or broken symlink), the current logic happily appends projects and only fails on that sub-path, yielding a misleading error.
Fail fast on the base path first and keep the existing projects check.

 	const envClaudeCodePath = process.env.CLAUDE_CONFIG_DIR?.trim() ?? '';
 	if (envClaudeCodePath === '') {
 		return DEFAULT_CLAUDE_CODE_PATH;
 	}

+	// Validate that the env path itself exists *and* is a directory
+	if (!isDirectorySync(envClaudeCodePath)) {
+		throw new Error(
+			`CLAUDE_CONFIG_DIR must point to an existing directory: ${envClaudeCodePath}`,
+		);
+	}
+
 	const claudeCodeProjectsPath = path.join(envClaudeCodePath, 'projects');

src/data-loader.ts (2)

41-44: Error message formatting nit

There is an unintended leading space and super-fluous newline in the thrown message.

-			` Claude data directory does not exist: ${claudeCodeProjectsPath}. 
+			`Claude data directory does not exist: ${claudeCodeProjectsPath}.
 			 Please set CLAUDE_CONFIG_DIR to a valid path, or ensure ${DEFAULT_CLAUDE_CODE_PATH} exists.

---

33-35: ESLint “unsafe-*” warnings originate from the untyped process.env access

Casting once avoids the cascade of ts/no-unsafe-* complaints:

-	const envClaudeCodePath = process.env.CLAUDE_CONFIG_DIR?.trim() ?? '';
+	const envClaudeCodePath = (process.env.CLAUDE_CONFIG_DIR ?? '').trim();

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro