Feature: Language-specific analyzers - Dart/Flutter, Svelte/TS, Go #233

Feature: Language-Specific Analyzers (Dart/Flutter, Svelte/TS, Go)

Problem

Cora treats all code as generic text. Language-specific patterns (Flutter widget lifecycle, Svelte reactive statements, Go error handling) are not recognized, leading to generic review feedback.

Proposed Solution

Add language-specific rule analyzers that understand language idioms and anti-patterns.

Priority Languages

Implementation

Add to LLM system prompt per detected language:

fn language_context(file: &str, content: &str) -> String {
    match detect_language(file) {
        Lang::Dart => DART_RULES,    // Widget lifecycle, async patterns
        Lang::Svelte => SVELTE_RULES, // Reactive stores, SSR considerations
        Lang::Go => GO_RULES,         // Error wrapping, goroutine safety
        _ => String::new(),
    }
}

Not a static analyzer — enriched prompts for LLM to understand language-specific context.

Why v0.5

• Requires quality profiles (feat: quality profiles — preset and configurable rule sets per project #208) to properly scope language rules
• Can be built incrementally — add one language at a time

Acceptance Criteria

• Dart/Flutter: detect widget lifecycle issues, state management anti-patterns
• Svelte/TS: detect reactive declaration issues, store misuse
• Go: detect unwrapped errors, goroutine leak patterns
• Language detection based on file extension
• Config toggle per language: languages.dart.enabled = true
• Each language adds <500ms to review time