Gemini CLI for Large Codebase Analysis

Use the Gemini CLI with its massive context window to analyze large codebases or multiple files that might exceed context limits.

Basic Syntax

gemini -p "@<path> <your question or prompt>"

The @ syntax includes files and directories in your prompt. Paths are relative to your current working directory.

File and Directory Inclusion

Single file

gemini -p "@src/main.py Explain this file's purpose and structure"

Multiple files

gemini -p "@package.json @src/index.js Analyze the dependencies used in the code"

Entire directory

gemini -p "@src/ Summarize the architecture of this codebase"

Multiple directories

gemini -p "@src/ @tests/ Analyze test coverage for the source code"

Current directory and subdirectories

gemini -p "@./ Give me an overview of this entire project"

Using --all_files flag

gemini --all_files -p "Analyze the project structure and dependencies"

Implementation Verification Examples

Check if a feature is implemented

gemini -p "@src/ @lib/ Has dark mode been implemented in this codebase? Show me the relevant files and functions"

Verify authentication implementation

gemini -p "@src/ @middleware/ Is JWT authentication implemented? List all auth-related endpoints and middleware"

Check for specific patterns

gemini -p "@src/ Are there any React hooks that handle WebSocket connections? List them with file paths"

Verify error handling

gemini -p "@src/ @api/ Is proper error handling implemented for all API endpoints? Show examples of try-catch blocks"

Check for rate limiting

gemini -p "@backend/ @middleware/ Is rate limiting implemented for the API? Show the implementation details"

Verify caching strategy

gemini -p "@src/ @lib/ @services/ Is Redis caching implemented? List all cache-related functions and their usage"

Check for security measures

gemini -p "@src/ @api/ Are SQL injection protections implemented? Show how user inputs are sanitized"

Verify test coverage

gemini -p "@src/payment/ @tests/ Is the payment processing module fully tested? List all test cases"

When to Use This Skill

• Analyzing entire codebases or large directories
• Comparing multiple large files
• Understanding project-wide patterns or architecture
• Current context window is insufficient for the task
• Working with files totaling more than 100KB
• Verifying if specific features, patterns, or security measures are implemented
• Checking for the presence of certain coding patterns across the entire codebase

Important Notes

• Paths in @ syntax are relative to your current working directory when invoking gemini
• The CLI will include file contents directly in the context
• No need for --yolo flag for read-only analysis
• Gemini's context window can handle entire codebases that would overflow Claude's context
• Be specific about what you're looking for to get accurate results