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 (3)

698-704: Critical: taking the address of a range variable stores the same pointer.

Using &task inside a range loop captures the loop variable's address, which is reused each iteration; all pointers end up pointing to the last element. This breaks selection, updates, and any pointer-based lookup.

Apply this diff to materialize a new variable per iteration:

-        for i, task := range msg.tasks {
-            task.UpdateListTitle()
-            task.UpdateListDesc()
-            tasks[i] = &task
-            m.taskMap[task.ID] = &task
-            m.taskIndexMap[task.ID] = i
-        }
+        for i := range msg.tasks {
+            t := msg.tasks[i] // copy to a new variable to take a stable address
+            t.UpdateListTitle()
+            t.UpdateListDesc()
+            tasks[i] = &t
+            m.taskMap[t.ID] = &t
+            m.taskIndexMap[t.ID] = i
+        }

---

712-716: Same pointer-of-range bug for inactive tasks.

All pointers will reference the last item.

Apply this diff:

-        for i, inactiveTask := range msg.tasks {
-            inactiveTask.UpdateListTitle()
-            inactiveTask.UpdateListDesc()
-            inactiveTasks[i] = &inactiveTask
-        }
+        for i := range msg.tasks {
+            t := msg.tasks[i]
+            t.UpdateListTitle()
+            t.UpdateListDesc()
+            inactiveTasks[i] = &t
+        }

---

199-199: Bug: clearing the wrong input collection (taskInputs vs tLInputs).

In editActiveTLView escape handling, this should clear time-log inputs, not task inputs.

Apply this diff:

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

internal/ui/model.go (1)

174-180: Derive “quick” frames from the default to avoid magic numbers.
Make the relationship explicit so future tuning stays consistent.

 func errMsgQuick(msg string) userMsg {
   return userMsg{
     value:      msg,
     kind:       userMsgErr,
-    framesLeft: 2,
+    framesLeft: userMsgDefaultFrames - 1,
   }
 }

internal/ui/view.go (1)

35-37: Reintroduce trimming to avoid layout break with long messages.
Directly rendering long messages can overflow the status bar. Trim to terminal width.

- if m.message.framesLeft > 0 && m.message.value != "" {
-   statusBar = m.message.value
- }
+ if m.message.framesLeft > 0 && m.message.value != "" {
+   statusBar = utils.Trim(m.message.value, m.terminalWidth)
+ }

internal/ui/model.go (3)

82-94: Typed, frame-limited user message model is a solid foundation. Minor nit on type.
The structure and kind enum look good. Consider shrinking framesLeft to uint8 (or using int) to avoid unsigned arithmetic footguns and to better communicate the small domain.

Apply this diff to narrow the field type:

 type userMsg struct {
   value      string
   kind       userMsgKind
-  framesLeft uint
+  framesLeft uint8
 }

---

129-129: Debug flag on Model is fine; consider harmonizing env handling across the app.
You now have DEBUG (for logging) and HOURS_DEBUG (for UI footer). Optional: unify semantics/naming or doc both in README for clarity.

---

165-172: Add a symmetric infoMsg helper (optional).
You already model info via userMsgInfo; adding a helper improves consistency with errMsg/errMsgQuick.

Example to add near these helpers:

func infoMsg(msg string) userMsg {
	return userMsg{
		value:      msg,
		kind:       userMsgInfo,
		framesLeft: userMsgDefaultFrames,
	}
}

internal/ui/ui.go (1)

23-25: Environment switch for UI debug is fine; consider broader truthiness.
Optional: accept any non-empty HOURS_DEBUG (or common truthy forms) instead of only "1", or document this strictness.

- debug := os.Getenv("HOURS_DEBUG") == "1"
+ // Alternative: treat any non-empty as enabled
+ debug := os.Getenv("HOURS_DEBUG") != ""

internal/ui/view.go (1)

306-314: Enrich debug footer (optional).
Consider including message kind for quick diagnostics; numeric enum is fine for debug.

- if m.debug {
-   footer = fmt.Sprintf("%s [term: %dx%d] [msg frames left: %d]",
-     footer,
-     m.terminalWidth,
-     m.terminalHeight,
-     m.message.framesLeft,
-   )
- }
+ if m.debug {
+   footer = fmt.Sprintf("%s [term: %dx%d] [msg frames left: %d] [msg kind: %d]",
+     footer,
+     m.terminalWidth,
+     m.terminalHeight,
+     m.message.framesLeft,
+     m.message.kind,
+   )
+ }

internal/ui/update.go (2)

39-46: TTL countdown logic is correct; small simplification possible.
Combine the two checks to avoid the second branch when framesLeft is 0.

-if m.message.framesLeft > 0 {
-  m.message.framesLeft--
-}
-
-if m.message.framesLeft == 0 {
-  m.message.value = ""
-}
+if m.message.framesLeft > 0 {
+  m.message.framesLeft--
+  if m.message.framesLeft == 0 {
+    m.message.value = ""
+  }
+}

---

39-46: Optional: make TTL time-based instead of event-based.
Right now TTL advances only on Update events. If you want “for a while” to mean wall-clock time, add a tea.Tick and decrement frames on ticks instead of key events.

internal/ui/handle.go (7)

27-27: Consistent use of wrappers; nit: reuse genericErrorMsg constant.

• Line 27: Good switch to errMsg for actionable validation feedback.
• Line 39: Prefer the existing genericErrorMsg constant over duplicating the literal.

Apply this diff:

-            m.message = errMsg("Something went wrong")
+            m.message = errMsg(genericErrorMsg)

Also applies to: 39-39

---

362-362: Consider making this info message shorter-lived (errMsgQuick).

"Nothing is being tracked right now" is ephemeral guidance; errMsgQuick may be a better UX fit unless you intentionally want a longer TTL.

Apply this diff:

-        m.message = errMsg("Nothing is being tracked right now")
+        m.message = errMsgQuick("Nothing is being tracked right now")

---

688-688: Fix spacing around colon in error message.

"Error fetching tasks: ..." reads correctly; current string has an extra space before the colon.

Apply this diff:

-        m.message = errMsg("Error fetching tasks : " + msg.err.Error())
+        m.message = errMsg("Error fetching tasks: " + msg.err.Error())

---

862-862: Consider longer-lived or sticky message for reload suggestion.

suggestReloadingMsg is multi-clause guidance that users may miss with a short TTL (errMsg framesLeft=3). Consider a longer-lived variant (e.g., errMsgFrames(5)) or a “sticky until next action” mode for such remedial instructions.

Also applies to: 872-872

---

208-211: Nit: avoid resetting the comment input inside the loop.

m.tLCommentInput.SetValue("") is called once per iteration; move it out of the loop.

Apply this diff:

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

---

489-490: Standardize timestamp precision for symmetry.

Start timestamps are truncated to the second (Line 489), but quick-switch uses time.Now() (Line 533) without truncation. For consistent display/comparison and to avoid off-by-subsecond surprises, consider truncating both.

Apply this diff:

-    return quickSwitchActiveIssue(m.db, task.ID, time.Now())
+    return quickSwitchActiveIssue(m.db, task.ID, time.Now().Truncate(time.Second))

Also applies to: 533-533

---

439-451: Optional copy tweak for deactivation message

– The “remove filter first” guardrail is clear and concise.
– The deactivation message can be smoothed out stylistically:

- m.message = errMsg("Cannot deactivate a task being tracked; stop tracking and try again.")
+ m.message = errMsg("Cannot deactivate a task that's being tracked. Stop tracking and try again.")

– Confirmed: msgCouldntSelectATask is defined in internal/ui/update.go (line 17), so this reference is safe.

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.