How scarowar/pear-review works
Main Components
a. VS Code Integration Layer
• Extension Host Process
• Command Registration System
• Status Bar Integration
• Editor Integration (for inline annotations)
b. Core Pear Review Engine
• Code Analysis Module
• Review Generation System
• Settings Management
• Git Integration Service
c. External Dependencies
• GitHub Copilot API
• Git System
• VS Code API
[VS Code Editor Layer] → [Pear Review Extension Layer] → [External Services Layer]
Component Relationships
Use the following connection types:
Key Flows
a. Review Trigger Flow:
• [File Save/Manual Trigger] → [Extension Host] → [Review Engine] → [Copilot API] → [Review Results] → [Editor Annotations]
b. Settings Flow:
• [VS Code Settings] → [Extension Config] → [Review Engine Behavior]
c. Git Integration Flow:
• [Git Working Directory] → [Git Service] → [Changed Files Detection] → [Review Scope]
Important Details
• Command Registration System showing the three main commands:
• Review
• Toggle Auto Review
• Toggle Review Annotations
• Editor Integration showing:
• Inline annotation system
• Review comment display
• Code change detection
Architectural Patterns to Highlight
• Event-driven architecture for VS Code integration
• Observer pattern for file changes
• Strategy pattern for different types of code analysis
• Factory pattern for review comment generation
Technical Stack Indicators
Following technologies:
• TypeScript (main implementation language)
• VS Code Extension API
• GitHub Copilot API
• Git