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.

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you open a pull request for review, mark a draft as ready, or comment "@codex review". If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex fix this CI failure" or "@codex address that feedback".

cmd/internal/migrations/v3/context_methods.go (2)

29-42: baseIdent misses common nodes (Index/Paren/TypeAssert/Star); extend to avoid skipped rewrites.

Without handling these, patterns like ctxs[i].Context() or (c).Context() won’t be rewritten.

Apply:

-				baseIdent := func(expr ast.Expr) *ast.Ident {
+				baseIdent := func(expr ast.Expr) *ast.Ident {
 					for {
 						switch e := expr.(type) {
 						case *ast.Ident:
 							return e
 						case *ast.SelectorExpr:
 							expr = e.X
 						case *ast.CallExpr:
 							expr = e.Fun
+						case *ast.IndexExpr:
+							expr = e.X
+						case *ast.IndexListExpr:
+							expr = e.X
+						case *ast.ParenExpr:
+							expr = e.X
+						case *ast.TypeAssertExpr:
+							expr = e.X
+						case *ast.StarExpr:
+							expr = e.X
 						default:
 							return nil
 						}
 					}
 				}

---

67-79: Regex-based UserContext→Context can alter strings/comments and misses complex receivers; prefer AST.

Consider an AST pass similar to fixSetUserContextCalls for X.UserContext() → X.Context() on fiber Ctx, covering chains and index expressions.

cmd/internal/migrations/v3/context_methods_test.go (1)

196-211: Consider an index-expression test (nice-to-have).

Covers ctxs[i].Context() and (c).Context() cases once baseIdent is extended.

Example:

func Test_MigrateContextMethods_IndexAndParen(t *testing.T) {
	t.Parallel()
	dir, err := os.MkdirTemp("", "mcmtest-index")
	require.NoError(t, err)
	defer func() { require.NoError(t, os.RemoveAll(dir)) }()
	file := writeTempFile(t, dir, `package main
import "github.com/gofiber/fiber/v2"
func handler(c fiber.Ctx, ctxs []fiber.Ctx) error {
    rc := ctxs[0].Context()
    _ = (c).Context().SetBodyStreamWriter(nil)
    _ = rc
    return nil
}`)
	var buf bytes.Buffer
	cmd := newCmd(&buf)
	require.NoError(t, v3.MigrateContextMethods(cmd, dir, nil, nil))
	content := readFile(t, file)
	assert.Equal(t, 2, strings.Count(content, ".RequestCtx()"))
}

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: ReneWerner87
PR: gofiber/contrib#0
File: :0-0
Timestamp: 2024-11-29T15:24:06.083Z
Learning: When customizing the Fiber context to achieve version independence, using generics in methods like `Status` and `Type` allows for fluent method chaining. Implementing a generic interface for `Ctx` on the `App` prevents class switching when registering custom contexts that use fluent methods. Providing multiple `New` methods allows users who do not wish to customize the context to continue using `fiber.New` without changes.

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: ReneWerner87
PR: gofiber/contrib#0
File: :0-0
Timestamp: 2024-11-29T15:24:06.083Z
Learning: When customizing the Fiber context to achieve version independence, using generics in methods like `Status` and `Type` allows for fluent method chaining. Implementing a generic interface for `Ctx` on the `App` prevents class switching when registering custom contexts that use fluent methods. Providing multiple `New` methods allows users who do not wish to customize the context to continue using `fiber.New` without changes.