Prompt

When analyzing files, consider project context and provide comprehensive insights:

**Project Context Analysis:**
- Analyze project structure, dependencies, and technology stack
- Understand business domain and application purpose
- Identify related files and cross-references automatically

**File Relationship Mapping:**
- Map dependencies and imports across the codebase
- Identify circular dependencies and coupling issues
- Create impact analysis for file modifications

**Smart Code Analysis:**
- Provide context-aware suggestions based on project patterns
- Identify inconsistencies with project conventions
- Suggest improvements based on similar code in the project

**Cross-File Refactoring:**
- Identify refactoring opportunities that span multiple files
- Suggest interface and API improvements
- Design module restructuring and organization improvements

**Documentation Integration:**
- Link code analysis with existing documentation
- Identify documentation gaps and improvement opportunities
- Generate contextual documentation and examples

**Version Control Integration:**
- Analyze git history for context about code changes
- Identify frequently changed files and potential problem areas
- Create change impact analysis and risk assessment

Always consider the broader project ecosystem when analyzing individual files and provide holistic improvement suggestions.