codebase-analyzer

# Codebase Analyzer

Understand existing codebase patterns and context to inform feature judgement.

## Purpose

Before judges evaluate a feature proposal, they need to understand:
- What similar features already exist?
- What's the tech stack and architecture?
- What patterns and conventions are used?
- What files/code would be affected?

This skill provides that context through hybrid search strategy (fast → deep as needed).

## Input

```typescript
interface AnalyzerInput {
  parsedProposal: ParsedProposal;  // From feature-parser
  workingDirectory: string;  // Current project root
}
```

Key data used from ParsedProposal:
- `keywords`: For searching similar features
- `constraints`: Tech stack hints (e.g., "Laravel 12.x")
- `requirements.mustHave`: Integration points to search for

## Strategy: Hybrid Search

### Phase 1: Targeted Fast Search (Always runs)

Quick reconnaissance using keywords:

**1. Identify Tech Stack:**
```markdown
Search for config/manifest files:
- package.json → Node.js, npm/yarn, frameworks (React, Vue, Express)
- composer.json → PHP, Composer, Laravel/Symfony
- requirements.txt / Pipfile → Python, Django/Flask
- go.mod → Go
- Cargo.toml → Rust
- pom.xml / build.gradle → Java
- Gemfile → Ruby, Rails

Use Glob tool:
- Glob pattern: "**/package.json"
- Glob pattern: "**/composer.json"
- Glob pattern: "**/requirements.txt"
- Glob pattern: "**/go.mod"

Read first match to extract:
- Language & version
- Framework & version
- Key dependencies
```

**2. Find Similar Features:**
```markdown
Use keywords from proposal to search:

Grep for keywords in code:
- Pattern: keywords joined with OR regex
- Example: "notification|notify|alert" if proposal is about notifications
- Output mode: "files_with_matches"
- File types: source code only (js, ts, py, php, go, rs, java, rb)

Example searches based on feature type:
- Notifications: grep "notification|notify|alert|email.*send"
- Authentication: grep "auth|login|session|token|jwt"
- API: grep "api|endpo