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.

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

186-219: Solid cross-file regression test; consider adding alias/ambiguity variants.

This test effectively proves the two-pass scan picks up ContextKey from a different file and migrates the handler accordingly. Two optional enhancements:

• Add a variant where the middleware import in the handler uses an alias (e.g., ka "…/keyauth"), to ensure replacements still work when the handler doesn't import the defining package directly.
• Add an ambiguity test where both csrf and keyauth set the same ContextKey (e.g., "token") in different files, and the handler imports only one of them—this catches wrong mapping selection.

If you want, I can draft these additional tests.

cmd/internal/migrations/v3/middleware_locals.go (4)

36-36: Import regex largely covers single and block imports; dot-imports remain a corner case.

Your pattern finds both aliased and non-aliased imports in and outside import blocks. Two small improvements:

• Normalize dot imports (import . "…/csrf") to avoid capturing alias="." and breaking downstream logic.
• Consider tolerating trailing comments.

You can normalize the alias immediately after matching:

-	reImport := regexp.MustCompile(`(?m)^\s*(?:import\s+)?(?:([\w\.]+)\s+)?"github\.com/gofiber/fiber/(?:v2|v3)/middleware/([\w]+)"`)
+	reImport := regexp.MustCompile(`(?m)^\s*(?:import\s+)?(?:([\w\.]+)\s+)?"github\.com/gofiber/fiber/(?:v2|v3)/middleware/([\w]+)"(?:\s*//.*)?$`)

and in both import-collection loops (shown further below):

-			if alias == "" {
+			if alias == "" || alias == "." {
 				alias = pkg
 			}

Dot-imports still won’t enable scanning Config{…} without a qualifier; if that’s in scope, it likely needs AST parsing. Marking as optional.

---

69-79: DRY: factor import harvesting into a small helper.

You repeat the alias→pkg extraction logic in both passes. Extract to a local helper to avoid drift and to apply the dot-import normalization in one place.

Example (no diff needed here, just a suggestion):

func collectFiberMiddlewareImports(re *regexp.Regexp, content string) map[string]string { … }

---

98-106: Config field cleanup works; be mindful of nested composites.

The removal via alias\.Config{[^}]*} plus removeConfigField passes the current tests (including comment stripping). If configs ever embed slices/maps with } inside, the [^}] class might stop early. Optional: move cleanup to AST in a follow-up if you encounter real-world false negatives.

---

41-48: Normalize dot-import alias during import harvesting.

Apply the same tweak in both passes so alias=="." becomes alias=pkg, avoiding malformed patterns downstream.

-			if alias == "" {
+			if alias == "" || alias == "." {
 				alias = pkg
 			}

Also applies to: 72-79

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: sixcolors
PR: gofiber/fiber#2922
File: middleware/cors/utils.go:63-71
Timestamp: 2024-10-08T19:06:06.583Z
Learning: The project uses the testify/assert package for assertions in unit tests.

Learnt from: efectn
PR: gofiber/fiber#3162
File: hooks_test.go:228-228
Timestamp: 2024-12-13T08:14:22.851Z
Learning: In Go test files, prefer using the `require` methods from the `testify` package for assertions instead of manual comparisons and calls to `t.Fatal` or `t.Fatalf`.

Learnt from: sixcolors
PR: gofiber/fiber#3016
File: middleware/session/store.go:164-167
Timestamp: 2024-10-02T23:03:31.727Z
Learning: Unit tests in this project use testify require.