Feature: Meta-agent for automated PR review with impact analysis

## Feature Request

Implement a meta-agent that automatically reviews pull requests to provide: 1) Clear summary of what the PR accomplished, and 2) Analysis of how changes potentially affect other areas of the codebase.

## Description

A meta-agent would act as an intelligent code reviewer that understands the entire codebase context and can identify ripple effects, potential breaking changes, and unexpected impacts that human reviewers might miss.

## Core Functionality

### 1. PR Summary Generation

#### What the PR Did
- High-level summary in plain English
- Technical breakdown of changes
- Feature additions vs bug fixes vs refactoring
- Business impact explanation
- User-facing changes highlighted
- Performance implications
- Security considerations

#### Automated Analysis
```javascript
class PRSummaryGenerator {
async analyzePR(prData) {
return {
summary: {
title: "Refactored authentication system",
type: "refactoring",
description: "Migrated from JWT to session-based auth",
changes: [
"Replaced JWT token generation with session management",
"Updated middleware for session validation",
"Modified user login/logout flows",
"Added session store with Redis"
],
metrics: {
filesChanged: 15,
linesAdded: 450,
linesRemoved: 320,
complexity: "medium",
risk: "high"
}
},
userImpact: [
"Users will need to re-authenticate",
"Session timeout now 24 hours (was unlimited)",
"Multiple device login now supported"
],
technicalDetails: {
patterns: ["Repository Pattern", "Middleware"],
dependencies: ["express-session", "redis"],
removedDependencies: ["jsonwebtoken"],
apiChanges: true,
databaseChanges: true
}
};
}
}
```

### 2. Codebase Impact Analysis

#### Ripple Effect Detection
- Identify all files importing changed modules
- Trace function call chains
- Detect interface/contract changes
- Find dependent services
- Locate affected tests
- Identify configuration dependencies

#### Impact Visualization
```javascript
class ImpactAnalyzer {
async analyzeImpact(changes) {
return {
directImpact: {
// Files directly modified
files: ["auth.js", "middleware.js"],
functions: ["authenticate", "validateSession"],
classes: ["AuthService", "SessionManager"]
},

indirectImpact: {
// Files that import/use changed code
consumers: [
{
file: "api/users.js",
usage: "Imports authenticate middleware",
risk: "HIGH - Breaking change in middleware signature",
suggestion: "Update middleware usage to new format"
},
{
file: "api/posts.js",
usage: "Uses req.user from auth",
risk: "LOW - Property structure unchanged",
suggestion: "Verify user object structure"
}
],

testFiles: [
"tests/auth.test.js - 5 tests will fail",
"tests/integration/api.test.js - 12 tests affected"
],

configurations: [
".env - New REDIS_URL required",
"docker-compose.yml - Add Redis service"
]
},

crossCutting: {
performance: "Session lookup adds ~5ms latency",
security: "Improved - sessions can be revoked",
scalability: "Requires Redis for horizontal scaling",
monitoring: "Update auth metrics dashboards"
}
};
}
}
```

## Implementation Features

### Intelligent Code Understanding

#### AST Analysis
- Parse code changes at syntax level
- Understand function signatures
- Track type changes
- Identify breaking changes
- Detect deprecated usage

#### Semantic Analysis
- Understand code intent
- Identify design patterns
- Recognize architectural changes
- Detect anti-patterns
- Suggest improvements

### Multi-Language Support
- JavaScript/TypeScript
- Python
- Go
- Java
- Ruby
- Support for mixed codebases

### Integration Points

#### Version Control
```javascript
class GitIntegration {
async getPRContext() {
return {
branch: 'feature/new-auth',
base: 'main',
commits: [...],
diff: await this.getDiff(),
history: await this.getRelatedPRs(),
author: await this.getAuthorContext()
};
}

async crossReferencePRs() {
// Find related changes
// Identify similar past PRs
// Learn from previous reviews
}
}
```

#### CI/CD Pipeline
- Run after tests pass
- Block merge on critical issues
- Generate review report
- Update PR description
- Add review comments
- Set approval status

### Review Output Format

#### Summary Report
```markdown
## 🤖 Meta-Agent PR Review

### What This PR Does
✅ **Main Changes:**
- Implements user notification system
- Adds email and push notification support
- Creates notification preferences UI

📊 **Statistics:**
- 12 files changed
- 500 lines added, 50 removed
- 3 new API endpoints
- 2 new database tables

### Potential Impacts

#### 🔴 High Risk Areas
1. **Authentication Service** (auth/service.js)
- Breaking change in login() method signature
- 15 consumers need updates
- Affects: Mobile app, admin panel, API gateway

2. **Database Migration**
- Requires downtime for migration
- Affects: All services using user table

#### 🟡 Medium Risk Areas
1. **API Rate Limiting** (middleware/rateLimit.js)
- New dependency on Redis
- May affect response times under load

#### 🟢 Low Risk Areas
1. **UI Components** (components/NotificationBell.jsx)
- Isolated component change
- No breaking changes

### Recommendations
1. ⚠️ Update API documentation
2. ⚠️ Add migration rollback script
3. ⚠️ Load test notification service
4. ✅ Consider feature flag for rollout
```

### Advanced Features

#### Learning System
- Learn from past reviews
- Identify recurring issues
- Suggest based on patterns
- Improve over time
- Team-specific preferences

#### Dependency Analysis
```javascript
class DependencyImpact {
async analyze() {
return {
npm: {
added: ["nodemailer@6.9.0"],
updated: ["express@4.18.0 -> 4.19.0"],
removed: ["legacy-mailer@1.0.0"],
vulnerabilities: "None detected",
bundleSize: "+15KB"
},

internal: {
affected: [
"Payment service - uses User model",
"Analytics service - tracks user events",
"Admin panel - user management affected"
]
},

external: {
apis: "No external API changes",
webhooks: "Notification webhooks added",
integrations: "Slack integration affected"
}
};
}
}
```

#### Test Impact
- Identify broken tests
- Suggest new test cases
- Coverage analysis
- Performance test results
- Integration test impacts

### Visualization

#### Impact Graph
- Interactive dependency graph
- Highlight affected paths
- Color-coded risk levels
- Clickable nodes to code
- Zoom/pan navigation

#### Change Timeline
- Show change progression
- Identify related commits
- Display refactoring patterns
- Track code evolution

## Configuration

```yaml
meta-agent:
enabled: true

analysis:
depth: 3 # How many levels deep to trace impacts
include_tests: true
include_docs: true
semantic_analysis: true

risk_thresholds:
high:
breaking_changes: true
affects_files: 10
complexity: 8
medium:
affects_files: 5
complexity: 5

notifications:
slack: true
email: false
block_merge_on_high_risk: true

learning:
enabled: true
use_historical_data: true
team_specific: true
```

## Benefits

- **Comprehensive Review**: Catches impacts humans might miss
- **Time Saving**: Instant analysis vs manual review
- **Risk Mitigation**: Identifies breaking changes early
- **Knowledge Sharing**: Documents changes clearly
- **Consistency**: Same quality review every time
- **Learning**: Improves based on feedback

## Acceptance Criteria

- [ ] PR summary accurately describes changes
- [ ] Impact analysis identifies all affected files
- [ ] Risk levels are accurately assessed
- [ ] Breaking changes are detected
- [ ] Test impacts are identified
- [ ] Dependencies changes are tracked
- [ ] Performance implications noted
- [ ] Security concerns highlighted
- [ ] Clear actionable recommendations
- [ ] Integration with GitHub PR UI
- [ ] Configurable risk thresholds
- [ ] Multi-language support works
- [ ] Learning system improves accuracy
- [ ] Visualization tools are intuitive
- [ ] Performance is acceptable (<30s analysis)

## Future Enhancements

- AI-powered code suggestions
- Automatic fix generation
- Cross-repository impact analysis
- Historical pattern matching
- Team coding standards enforcement
- Automated refactoring suggestions
- Cost analysis (cloud resources)
- Compliance checking

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

No repository files or tests are named. Start by mapping the existing GitHub pull-request and review integration, then define a narrowly scoped first slice from the requested summary or impact analysis before evaluating the broader acceptance criteria. Done should be demonstrated with tests and a working PR review result, but the issue does not specify the implementation boundaries.

Written by the indexing model from the issue text.