fix: Docker path translation for review_changes and code deduplication

- Fixed review_changes tool to properly translate host paths to container paths in Docker
- Prevents "No such file or directory" errors when running in Docker containers
- Added proper error handling with clear messages when paths are inaccessible

refactor: Centralized token limit validation across all tools
- Added _validate_token_limit method to BaseTool to eliminate code duplication
- Reduced ~25 lines of duplicated code across 5 tools (analyze, chat, debug_issue, review_code, think_deeper)
- Maintains exact same error messages and behavior

feat: Enhanced large prompt handling
- Added support for prompts >50K chars by requesting file-based input
- Preserves MCP's ~25K token capacity for responses
- All tools now check prompt size before processing

test: Added comprehensive Docker path integration tests
- Tests for path translation, security validation, and error handling
- Tests for review_changes tool specifically with Docker paths
- Fixed failing think_deeper test (updated default from "max" to "high")

chore: Code quality improvements
- Applied black formatting across all files
- Fixed import sorting with isort
- All tests passing (96 tests)
- Standardized error handling follows MCP TextContent format

The changes ensure consistent behavior across all environments while reducing code duplication and improving maintainability.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>

prompts/__init__.py

@@ -2,13 +2,8 @@
 System prompts for Gemini tools
 """
 
-from .tool_prompts import (
-    ANALYZE_PROMPT,
-    CHAT_PROMPT,
-    DEBUG_ISSUE_PROMPT,
-    REVIEW_CODE_PROMPT,
-    THINK_DEEPER_PROMPT,
-)
+from .tool_prompts import (ANALYZE_PROMPT, CHAT_PROMPT, DEBUG_ISSUE_PROMPT,
+                           REVIEW_CODE_PROMPT, THINK_DEEPER_PROMPT)
 
 __all__ = [
     "THINK_DEEPER_PROMPT",

prompts/tool_prompts.py

@@ -16,6 +16,10 @@ Your role is to:
 4. Focus on aspects Claude might have missed or couldn't fully explore
 5. Suggest implementation strategies and architectural improvements
 
+IMPORTANT: Your analysis will be critically evaluated by Claude before final decisions are made. 
+Focus on providing diverse perspectives, uncovering hidden complexities, and challenging assumptions 
+rather than providing definitive answers. Your goal is to enrich the decision-making process.
+
 Key areas to consider (in priority order):
 1. **Security vulnerabilities and attack vectors** - This is paramount. Consider:
    - Authentication/authorization flaws