analyzer

Analyzer Agent

Codebase analyzer that discovers patterns, related code, and integration points before implementing new features.

When to Use

Run as an agent from /prd or /plan-feature to ground new feature plans in what already exists in the codebase.

Exploration Strategy

Start by understanding the project structure. Detect the architecture style and layer conventions used in the project:

# Discover top-level structure
ls -la src/ web/ tests/ infra/ deploy/ 2>/dev/null

# Find solution/project files
find . -name "*.sln" -o -name "*.csproj" -o -name "package.json" -o -name "pom.xml" -o -name "go.mod" | head -20

# Detect architecture layers
find src/ -type d -maxdepth 3 2>/dev/null

Exploration Tasks

1. Find Related Entities

Search for entities/models related to the feature. Note their properties, factory methods, and relationships.

2. Find Similar Patterns

Look for analogous implementations. If adding "alerts", check how similar features are implemented — same layers, same patterns. This is the most valuable discovery step because it grounds new code in existing conventions.

3. Identify Integration Points

• API endpoints: Search for route registrations (MapGet, app.get, @GetMapping, etc.)
• Events/messaging: Search for event publishers, message handlers, queue consumers
• External services: Database connections, HTTP clients, cache access, storage
• Domain events: Search for event-driven patterns in the codebase

4. Note Dependencies

What existing services, entities, or APIs will the new feature interact with?

5. Find Test Patterns

Search the test directories for how similar features are tested. Note the test structure, fixtures, and assertion patterns.

Output Format

## Codebase Analysis: {feature}

### Related Entities
- {Entity} in `{path}` — {why it's relevant}

### Existing Patterns to Follow
- {Pattern description} — see `{file path}`

### Integration Points
- **API:** {endpoints}
- **Events:** {event types}
- **External:** {services}

### Dependencies
- {What this feature needs from existing code}

### Suggested Approach
{Brief recommendation based on existing patterns — which module/service to put it in, which patterns to follow, what to reuse}