Synthvora Growth
Coding

Gemini Code Assist Prompts

10 ready-to-use prompts

Researched for Gemini Code Assist real features. Replace the [BRACKETED] parts with your own details, copy, and paste.

1Agent Mode Feature Build
Use Gemini Code Assist agent mode in [IDE_NAME] to build this feature: '[FEATURE_DESCRIPTION]' for [PROJECT_NAME]. The change spans [FILE_1], [FILE_2], and [FILE_3]. Ask the agent to plan the multi-file edit first, show the plan, and only then execute. Require it to run [TEST_COMMAND] after the edit and fix any failures itself. Review the final diff for [CONCERN] before accepting, and keep the request inside the Standard tier budget of [REQUESTS] agent requests/day.
Tip: Ask for the plan before the edit; agent mode is powerful but plans are where you stay in control.
2Custom Command Library
Build a custom command library for Gemini Code Assist on my [TEAM_NAME] team. Define commands: /[CMD_1] to generate [OUTPUT_1] from selected code, /[CMD_2] to check [CHECK], and /[CMD_3] to scaffold [SCAFFOLD]. Pair each with rules engine entries enforcing [CONVENTION_1] and [CONVENTION_2] from our [STYLE_GUIDE]. Store the definitions in [CONFIG_PATH], share them via [SHARE_METHOD], and onboard [NUMBER] engineers with a [MINUTES]-minute walkthrough.
Tip: Name commands as verbs your team already uses; adoption dies on clever-but-cryptic names.
3Enterprise Code Customization
Set up Gemini Code Assist Enterprise code customization for [COMPANY_NAME] by ingesting our [VCS] repositories ([REPO_1], [REPO_2]). The goal: suggestions that follow our internal [LIBRARY_NAME] library and [PATTERN] patterns. Define the indexing scope (exclude [EXCLUDE_PATH]), verify data residency in [REGION], and confirm suggestions cite [SOURCE] sources. Pilot with the [TEAM] team for [WEEKS] weeks, measuring suggestion acceptance rate against the [BASELINE]% baseline.
Tip: Exclude generated code and vendored deps from indexing; they poison customization quality.
4Gemini CLI Automation Script
Write a Gemini CLI automation for [TASK_DESCRIPTION] that runs in [ENVIRONMENT]. The script should: 1) use agent mode to [STEP_1], 2) call [MCP_TOOL] via MCP for [STEP_2], 3) write results to [OUTPUT_FILE]. It must stay within the [TIER] tier quota of [REQUESTS] agent requests/day and handle rate limits (2 requests/second) with backoff. Test it on [TEST_INPUT] and log every run to [LOG_FILE] for the [WEEKS]-week pilot.
Tip: Add retry with backoff for the 2 req/sec rate limit; CLI scripts hit it faster than you expect.
5GitHub PR Review Bot Setup
Configure the Gemini Code Assist GitHub app to auto-review pull requests on [REPO_NAME]. Set it to post severity-rated findings on every PR to [BRANCH], respond to /gemini review and /gemini summary commands, and skip [PATHS] paths. Define the severity mapping: [SEVERITY_1] blocks merge via [BRANCH_PROTECTION], [SEVERITY_2] is advisory. Since new org installs closed in June 2026, verify our existing installation still receives reviews at the promised [NUMBER]+ PR reviews/day quota.
Tip: Verify your install date; orgs installed after June 2026 cannot add the GitHub app fresh.
6Framework Migration with Agent Mode
Migrate [PROJECT_NAME] from [OLD_FRAMEWORK] to [NEW_FRAMEWORK] using Gemini Code Assist agent mode. Scope: [NUMBER] files in [DIRECTORY]. Have the agent plan the migration per module, starting with [MODULE_1], update imports and APIs per the [MIGRATION_GUIDE], and run [TEST_COMMAND] after each module. Ask it to flag deprecated APIs with no direct replacement in [FLAG_FILE]. Keep a migration log in [LOG_FILE] and review the diff module by module.
Tip: Migrate module by module with tests green between each; agent mode is fast but verification is yours.
7Quota Budgeting Plan
Plan Gemini Code Assist usage for my [TEAM_SIZE]-person team on the [TIER] tier ($[PRICE]/user/month). Budget: [AGENT_REQUESTS] agent requests/day and [CHAT_REQUESTS] completion/chat requests/day shared across [IDE_1] and [IDE_2]. Allocate [PCT]% to agent mode, [PCT]% to chat, [PCT]% to completions. Set up [ALERT_METHOD] alerts at [PCT]% quota usage, and define the fallback (manual work or [FALLBACK_TOOL]) when the daily quota is exhausted.
Tip: Monitor the first two weeks closely; teams always underestimate how fast agent mode burns quota.
8Android Studio Mobile Build
Use Gemini Code Assist in Android Studio to build [APP_NAME], a [PLATFORM] app that [CORE_FUNCTION]. Have it generate the [SCREEN_1] screen with [UI_TOOLKIT], wire the [API] data layer with [NETWORKING_LIB], and handle the [PERMISSION] permission flow. Ask for code that follows [ARCHITECTURE, e.g. MVVM] with [DI_FRAMEWORK] for injection. Test on [EMULATOR] and the [DEVICE] physical device, fixing every warning the IDE surfaces.
Tip: Ask for the architecture pattern explicitly; generated Android code without one becomes spaghetti fast.
9Test Suite Generation
Have Gemini Code Assist generate a test suite for [MODULE_NAME] in [LANGUAGE] using [TEST_FRAMEWORK]. Cover [SCENARIO_1], [SCENARIO_2], and the regression case from bug [BUG_ID]. Ask it to follow the arrange-act-assert style in [EXAMPLE_TEST], mock [DEPENDENCY] with [MOCK_LIB], and target [COVERAGE]% coverage. Run the suite in [CI_TOOL], fix the [NUMBER] failing tests it generates itself, and require the suite green before merging PR #[PR_NUMBER].
Tip: Make the agent fix its own failing tests; accepting red generated tests normalizes broken suites.
10Antigravity Free Path for Individuals
Set up a free individual workflow now that Gemini Code Assist IDE extensions no longer serve the free tier (since June 18, 2026). Route personal projects through Google Antigravity, which carries the free Individual plan, for [PROJECT_TYPE] work in [LANGUAGE]. Document what still works free ([FEATURE_1], [FEATURE_2]) versus what needs a paid Standard seat ($19/user/month): [PAID_FEATURE]. Define the upgrade trigger: when [USAGE_METRIC] exceeds [THRESHOLD], move to paid.
Tip: Check the current free-tier routing before relying on it; Google moved it once and may move it again.
Back to all 214 platforms