{{ message }}
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.

There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💡 Verification agent
🧩 Analysis chain
Derive the CI directory from GEMINI_CONFIG_DIR and avoid duplicating the '.gemini' literal
Right now we hard-code '.gemini' here, while the rest of the module already imports GEMINI_CONFIG_DIR. Basing the CI branch on GEMINI_DIR avoids future drift if the core value changes and keeps a single source of truth. This also lets us drop the extra internal variable.
Apply this minimal diff within the same lines:
Optional hardening (outside the selected lines): if you want stricter CI detection across providers, consider normalizing CI to boolean and adding a brief JSDoc explaining why we diverge in CI.
Verification script to spot remaining hard-coded occurrences and ensure consistency across the repo:
Expected: Any remaining hard-coded '.gemini' (e.g., scripts/telemetry.js) are intentional or get refactored to use the same source of truth to prevent divergence between scripts and the CLI.
🏁 Script executed:
Length of output: 35731
Derive the CI directory from GEMINI_CONFIG_DIR and centralize the “.gemini” literal
Use the imported
GEMINI_CONFIG_DIR(aliased asGEMINI_DIR) to decide the CI path, drop theCUSTOM_DIRECTORY_NAMEhelper, and inline the conditional:• Remove
CUSTOM_DIRECTORY_NAMEand inline theCIcheck againstGEMINI_DIR.• (Optionally) Add a JSDoc on
SETTINGS_DIRECTORY_NAMEto explain the CI divergence and normalizeCIto a boolean.Mandatory follow-ups:
SETTINGS_DIRECTORY_NAME(orGEMINI_DIR) fromsettings.tsto avoid a second source of truth.'.gemini'and'.gen-cli'(in scripts, tests, etc.) and switch them to the centralized constants where appropriate.This ensures a single source of truth for all Gemini-related directory names and prevents future drift.
🤖 Prompt for AI Agents