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 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. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

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.

internal/ui/handle.go (1)

199-201: Bug: clearing the wrong input slice in editActiveTLView.

You’re clearing taskInputs instead of TL inputs when handling Escape for editActiveTLView. This wipes the task summary field instead of the begin timestamp.

Apply:

-    m.taskInputs[entryBeginTS].SetValue("")
+    m.tLInputs[entryBeginTS].SetValue("")

internal/ui/update.go (1)

167-173: ‘q’ does not go back in forms (help says q/ go back).

Currently, Escape in forms routes to handleEscapeInForms(), but ‘q’ falls through to handleRequestToGoBackOrQuit(), which doesn’t handle form views—so ‘q’ is a no-op in forms. This contradicts the help text and will confuse users.

Apply this to align ‘q’ with Escape in forms:

-        case "q", escape:
-            shouldQuit := m.handleRequestToGoBackOrQuit()
+        case "q", escape:
+            // Treat 'q' like Escape in form views
+            switch m.activeView {
+            case taskInputView, editActiveTLView, finishActiveTLView, manualTasklogEntryView, editSavedTLView:
+                m.handleEscapeInForms()
+                return m, tea.Batch(cmds...)
+            }
+            shouldQuit := m.handleRequestToGoBackOrQuit()
             if shouldQuit {
                 return m, tea.Quit
             }

internal/ui/update.go (2)

80-85: Escape focuses only forms here; consider a safety net.

This block handles Escape in form views only. If new form views are added, they’ll need to be added here as well.

Document this requirement or add a default branch to handle future form views defensively.

---

49-144: Two separate key-handling switch blocks reduce maintainability.

Key handling happens in two disjoint switches (Lines 49–144 and again at 164–279). Centralizing into one would reduce drift and double-handling risk.

Also applies to: 164-279

internal/ui/handle.go (1)

205-211: Move comment clearing out of the loop.

m.tLCommentInput.SetValue("") is called on each iteration unnecessarily.

Apply:

-    for i := range m.tLInputs {
-        m.tLInputs[i].SetValue("")
-        m.tLCommentInput.SetValue("")
-    }
+    for i := range m.tLInputs {
+        m.tLInputs[i].SetValue("")
+    }
+    m.tLCommentInput.SetValue("")

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

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.