Gemini can import a GitHub repository or code folder in supported web workflows. Current documented limits and mobile availability vary; imported repository content is a snapshot rather than a live sync.
1. Import the exact branch you care about
Use the code import flow and choose the repository or branch relevant to the question. For private code, verify you are linking the intended GitHub account.
2. Ask for an architecture map first
Request entry points, major modules, data flow, build/test commands and the likely ownership of the feature you care about. This creates a map before deep questioning.
3. Trace one behavior end to end
Choose one concrete request, UI action, API route or bug. Ask Gemini to trace definitions and callers with file paths rather than giving a generic explanation.
4. Check code claims against the snapshot
Open the cited files or compare with GitHub. If the repository changed after import, re-import or start a fresh chat instead of assuming the snapshot updated.
5. Turn findings into a bounded next action
Ask for a minimal change plan or review checklist, not a giant rewrite. Use an actual coding environment for edits, tests and version control.
Map this repository before proposing changes. Identify entry points, main modules, test commands and the files involved in [behavior]. Then trace that behavior with file paths and call relationships. Treat this import as a snapshot and flag any uncertainty.
Assuming the repository stays synced; importing the wrong branch; asking for broad changes before understanding architecture; treating an analysis chat as a substitute for compiling and testing code.
Finish check
You can name the snapshot/branch, key modules and exact files behind one behavior, and you know what must be re-imported or verified before acting.