targeted-analysis.md•2.99 kB
# Targeted Component Analysis Prompt Template
This template is used by the `gemini_targeted_analysis` tool to structure focused analysis requests to Gemini CLI.
## Prompt Structure
```
You are analyzing specific components of a codebase. Focus your analysis on the provided files/folders and their interactions with the broader system.
## Analysis Target
Files/Folders: [TARGET_PATHS_LIST]
## Analysis Framework
Provide focused insights covering:
### 1. Component Purpose & Responsibility
- What these files/modules accomplish
- Single Responsibility Principle adherence
- Clear separation of concerns
### 2. Dependencies & Integration
- How these components connect to other parts of the system
- Coupling analysis (tight vs loose coupling)
- Interface design and API patterns
- External dependencies and their management
### 3. Code Quality & Patterns
- Specific code quality issues in these components
- Design patterns usage and appropriateness
- Naming conventions and code readability
- Error handling within these components
### 4. Testing Coverage
- Test gaps specific to these components
- Testing recommendations and priorities
- Mock/stub requirements for isolated testing
- Integration test considerations
### 5. Performance Impact
- Performance characteristics of these components
- Bottlenecks or optimization opportunities
- Resource usage patterns
- Caching opportunities
### 6. Refactoring Priorities
- Specific improvements ranked by impact for these components
- Breaking change considerations
- Migration strategies if applicable
- Backward compatibility requirements
## Component Code Context
[TARGETED_CODEBASE_CONTENT_FROM_CODE2PROMPT]
## Instructions
Focus specifically on the provided components while considering their role in the larger system. Provide concrete, actionable recommendations with examples where possible.
```
## Key Features
- **Focused Scope**: Analyzes only specified files/folders
- **System Context**: Considers component relationships within larger system
- **Targeted Insights**: Provides specific recommendations for analyzed components
- **Integration Aware**: Addresses coupling and dependency concerns
- **Test Focused**: Emphasizes testing strategies for specific components
## Usage Notes
- Target paths are automatically populated from the tool call arguments
- Analysis includes only the specified files/folders via code2prompt filtering
- Results focus on the specific components while maintaining system awareness
- Designed for debugging, component reviews, and focused refactoring efforts
## Example Target Scenarios
### API Layer Analysis
```
targetPaths: ["src/api/", "src/controllers/"]
```
### Authentication System Review
```
targetPaths: ["src/auth/", "src/middleware/auth.js"]
```
### Database Integration Analysis
```
targetPaths: ["src/models/", "src/database/", "prisma/schema.prisma"]
```
### Frontend Component Review
```
targetPaths: ["src/components/UserProfile/", "src/hooks/useUser.ts"]
```