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/api/ctx.md (4)

13-13: Polish phrasing: “no-op(s)” and sentence flow

Suggest tightening wording and using the conventional “no-op(s)”.

-`Ctx` implements `context.Context`. However due to [current limitations in how fasthttp](https://github.com/valyala/fasthttp/issues/965#issuecomment-777268945) works, `Deadline()`, `Done()` and `Err()` operate as a nop. The `fiber.Ctx` instance is reused after the handler returns and must not be used for asynchronous operations once the handler has completed. Call [`Context`](#context) within the handler to obtain a `context.Context` that can be used outside the handler.
+`Ctx` implements `context.Context`. However, due to [current fasthttp limitations](https://github.com/valyala/fasthttp/issues/965#issuecomment-777268945), `Deadline()`, `Done()`, and `Err()` are no-ops. The `fiber.Ctx` instance is reused after the handler returns and must not be used for asynchronous operations once the handler has completed. Call [`Context`](#context) within the handler to obtain a `context.Context` that can be used outside the handler.

---

22-31: Add an async-safe example using c.Context()

The text advises using Context() for work outside the handler; add a short companion example to demonstrate it.

 ```go title="Example"
 func doSomething(ctx context.Context) {
   // ...
 }
 
 app.Get("/", func(c fiber.Ctx) error {
   doSomething(c)
+  // For asynchronous work, derive a context that is safe after the handler returns:
+  ctx := c.Context()
+  go doAsyncWork(ctx)
+  return nil
 })

---

`37-41`: **Show type assertion when using Value**

`Value` returns `any`; demonstrating a type assertion improves correctness and mirrors the `Locals` example below.



```diff
 app.Get("/", func(c fiber.Ctx) error {
   c.Locals(userKey, "admin")
-  user := c.Value(userKey) // returns "admin"
+  user, _ := c.Value(userKey).(string) // "admin"
+  _ = user
 })

---

96-96: Fix spelling: “cancellation”

Minor spelling issue.

-Sets the base `context.Context` used by [`Context`](#context). Use this to
-propagate deadlines, cancelation signals, or values to asynchronous operations.
+Sets the base `context.Context` used by [`Context`](#context). Use this to
+propagate deadlines, cancellation signals, or values to asynchronous operations.

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.

Learnt from: gaby
PR: gofiber/fiber#3193
File: middleware/cache/cache_test.go:897-897
Timestamp: 2024-11-08T04:10:42.990Z
Learning: In the Fiber framework, `Context()` is being renamed to `RequestCtx()`, and `UserContext()` to `Context()` to improve clarity and align with Go's context conventions.

Learnt from: gaby
PR: gofiber/fiber#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`.

Learnt from: gaby
PR: gofiber/fiber#3193
File: middleware/cache/cache_test.go:897-897
Timestamp: 2024-11-08T04:10:42.990Z
Learning: In the Fiber framework, `Context()` is being renamed to `RequestCtx()`, and `UserContext()` to `Context()` to improve clarity and align with Go's context conventions.

Learnt from: gaby
PR: gofiber/fiber#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`.