allowed-tools | description |
---|---|
Bash(gemini:*), Bash(cd:*), Bash(ls:*), Bash(pwd:*) |
Use `gemini` to analyze large codebases with massive context window |
When you need to debug issues involving a large size of related code relationships in the codebase, or when analyzing entire project, use gemini
Use gemini -p
to leverage Gemini's large context capacity. The @
syntax includes files and directories in your prompts. Paths should be relative to WHERE you run the gemini command.
cd /path/to/project
gemini -p "@src/main.py Explain this file's purpose and structure"
gemini -p "@package.json @src/index.js Analyze the dependencies used in the code"
gemini -p "@src/ Summarize the architecture of this codebase"
gemini -p "@src/ @tests/ Analyze test coverage for the source code"
gemini -p "@./ Give me an overview of this entire project"
# Or use --all_files flag:
gemini --all_files -p "Analyze the project structure and dependencies"
gemini -p "@src/ @lib/ Has dark mode been implemented in this codebase? Show me the relevant files and functions"
gemini -p "@src/ @middleware/ Is JWT authentication implemented? List all auth-related endpoints and middleware"
gemini -p "@src/ Are there any React hooks that handle WebSocket connections? List them with file paths"
gemini -p "@src/ @api/ Is proper error handling implemented for all API endpoints? Show examples of try-catch blocks"
gemini -p "@backend/ @middleware/ Is rate limiting implemented for the API? Show the implementation details"
gemini -p "@src/ @lib/ @services/ Is Redis caching implemented? List all cache-related functions and their usage"
gemini -p "@src/ @api/ Are SQL injection protections implemented? Show how user inputs are sanitized"
gemini -p "@src/payment/ @tests/ Is the payment processing module fully tested? List all test cases"
Use gemini -p
when:
- Analyzing entire codebases or large directories
- Comparing multiple large files
- Need to understand project-wide patterns or architecture
- Current context window is insufficient for the task
- Working with files totaling more than 100KB, PDF documents, or images
- Verifying if specific features, patterns, or security measures are implemented
- Checking for the presence of certain coding patterns across the entire codebase
- 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
- When checking implementations, be specific about what you're looking for to get accurate results
$ARGUMENTS