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.

docs/whats_new.md (2)

893-898: Add a quick “how to install” tip for the external utils module

Recommend adding an explicit go get step and noting the Go 1.25+ requirement to preempt user friction (your CI also flagged the newer Go requirement). This keeps the section self-contained and actionable.

Apply this diff to append a tip block under the first paragraph:

 ## 🛠️ Utils {#utils}

 Fiber v3 removes the built-in `utils` directory and now imports utility helpers from the separate [`github.com/gofiber/utils`](https://github.com/gofiber/utils) module. See the [migration guide](#utils-migration) for detailed replacement steps and examples.
 
 The `github.com/gofiber/utils` module also introduces new helpers like `ParseInt`, `ParseUint`, `Walk`, `ReadFile`, and `Timestamp`.
+
+:::tip Quick install
+Make sure you’re on Go 1.25 or newer, then add the module:
+
+```sh
+go get github.com/gofiber/utils@latest
+```
+:::

---

1914-1991: Tighten the Utils migration section: numbering, a clarifying note, and a couple of usage examples

• The ordered list restarts at “1.” multiple times. Markdown auto-numbers, but using 1/2/3 reads cleaner in raw view.
• Add a short note explaining the mapping convention (…Bytes → utils byte helpers; string funcs → standard library) to avoid confusion when scanning the table.
• Include tiny examples for new helpers (ParseInt, Timestamp) to show intended use at a glance.

Apply this diff:

-### 🛠️ Utils {#utils-migration}
+### 🛠️ Utils {#utils-migration}
 
 Fiber v3 removes the in-repo `utils` package in favor of the external [`github.com/gofiber/utils`](https://github.com/gofiber/utils) module.
 
-1. Replace imports:
+1. Replace imports:
 
 ```go
 - import "github.com/gofiber/fiber/v2/utils"
 + import "github.com/gofiber/utils"

-1. Review function changes:
+2. Review function changes:
+
+Note: functions that previously ended with ...Bytes map to byte-slice helpers in github.com/gofiber/utils. Plain string helpers are now covered by the Go standard library (strings/bytes) where noted.

v2 function	v3 replacement
AssertEqual	removed; use testing libraries like stretchr/testify
ToLowerBytes	utils.ToLowerBytes
ToUpperBytes	utils.ToUpperBytes
TrimRightBytes	utils.TrimRight
TrimLeftBytes	utils.TrimLeft
TrimBytes	utils.Trim
EqualFoldBytes	utils.EqualFold
UUID	utils.UUID
UUIDv4	utils.UUIDv4
FunctionName	utils.FunctionName
GetArgument	utils.GetArgument
IncrementIPRange	utils.IncrementIPRange
ConvertToBytes	utils.ConvertToBytes
CopyString	utils.CopyString
CopyBytes	utils.CopyBytes
ByteSize	utils.ByteSize
ToString	utils.ToString
UnsafeString	utils.UnsafeString
UnsafeBytes	utils.UnsafeBytes
GetString	removed; use utils.ToString or the standard library
GetBytes	removed; use utils.CopyBytes or []byte(s)
ImmutableString	removed; strings are already immutable
GetMIME	utils.GetMIME
ParseVendorSpecificContentType	utils.ParseVendorSpecificContentType
StatusMessage	utils.StatusMessage
IsIPv4	utils.IsIPv4
IsIPv6	utils.IsIPv6
ToLower	utils.ToLower
ToUpper	utils.ToUpper
TrimLeft	strings.TrimLeft
Trim	strings.Trim
TrimRight	strings.TrimRight
EqualFold	strings.EqualFold
StartTimeStampUpdater	utils.StartTimeStampUpdater (new utils.Timestamp provides the current value)

-1. Update your code. For example:
+3. Update your code. For example:

// v2
import oldutils "github.com/gofiber/fiber/v2/utils"

func demo() {
    b := oldutils.TrimBytes([]byte(" fiber "))
    id := oldutils.UUIDv4()
    s := oldutils.GetString([]byte("foo"))
}

// v3
import (
    "github.com/gofiber/utils"
    "strings"
)

func demo() {
    b := utils.Trim([]byte(" fiber "))
    id := utils.UUIDv4()
    s := utils.ToString([]byte("foo"))
    t := strings.TrimRight("bar  ", " ")
}

-The github.com/gofiber/utils module also introduces new helpers like ParseInt, ParseUint, Walk, ReadFile, and Timestamp.
+The github.com/gofiber/utils module also introduces new helpers like ParseInt, ParseUint, Walk, ReadFile, and Timestamp.
+
+go +// Examples +v, err := utils.ParseInt[int]("42") // -> 42, nil +nowUnixMilli := utils.Timestamp() // current cached unix ms (updated by StartTimeStampUpdater) +

</blockquote></details>

</blockquote></details>

<details>
<summary>📜 Review details</summary>

**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.

<details>
<summary>📥 Commits</summary>

Reviewing files that changed from the base of the PR and between edd70830728f4f09bcc2421dce07e7934f91fd03 and 185eaf6e0dfda33c67c71158227aaca2552b1992.

</details>

<details>
<summary>📒 Files selected for processing (1)</summary>

* `docs/whats_new.md` (4 hunks)

</details>

<details>
<summary>🧰 Additional context used</summary>

<details>
<summary>📓 Path-based instructions (1)</summary>

<details>
<summary>docs/**</summary>


**📄 CodeRabbit inference engine (.github/copilot-instructions.md)**

> Review and update the contents of the `docs` folder if necessary when modifying code

Files:
- `docs/whats_new.md`

</details>

</details><details>
<summary>🧠 Learnings (3)</summary>

<details>
<summary>📓 Common learnings</summary>

Learnt from: ckoch786
PR: #3230
File: docs/whats_new.md:944-951
Timestamp: 2024-12-15T19:56:45.935Z
Learning: Detailed usage examples and explanations for new methods like RemoveRoute and RemoveRouteByName are documented in docs/api/app.md, so it's unnecessary to duplicate them in docs/whats_new.md.

Learnt from: ReneWerner87
PR: #3161
File: app.go:923-932
Timestamp: 2024-11-15T07:56:21.623Z
Learning: In the Fiber framework, breaking changes are acceptable when moving from version 2 to version 3, including modifications to method signatures such as in the Test method in app.go.

</details>
<details>
<summary>📚 Learning: 2024-11-15T07:56:21.623Z</summary>

Learnt from: ReneWerner87
PR: #3161
File: app.go:923-932
Timestamp: 2024-11-15T07:56:21.623Z
Learning: In the Fiber framework, breaking changes are acceptable when moving from version 2 to version 3, including modifications to method signatures such as in the Test method in app.go.

**Applied to files:**
- `docs/whats_new.md`

</details>
<details>
<summary>📚 Learning: 2024-11-10T23:44:13.704Z</summary>

Learnt from: gaby
PR: #3193
File: middleware/adaptor/adaptor.go:111-111
Timestamp: 2024-11-10T23:44:13.704Z
Learning: In the middleware/adaptor/adaptor.go file of the Fiber framework, when updating context handling, replacing c.Context() with c.RequestCtx() is appropriate to access the fasthttp.RequestCtx.

**Applied to files:**
- `docs/whats_new.md`

</details>

</details>

</details>

</details>

<details>
<summary>🔇 Additional comments (2)</summary><blockquote>

<details>
<summary>docs/whats_new.md (2)</summary><blockquote>

`27-27`: **TOC entry for Utils looks good**

The anchor matches the new section id (`#utils`) introduced below. No action needed.

---

`1414-1414`: **Migration guide TOC entry is correct**

The link (`#utils-migration`) correctly points to the new migration subsection id below. Looks good.

</blockquote></details>

</blockquote></details>

<!-- This is an auto-generated comment by CodeRabbit for review status -->