Skip to content

Phase 4: Impact analysis & dead code detection as deterministic findings #459

Closed

Description

@ajianaz

Add deterministic findings from code graph: high-impact change detection (review) and dead code detection (scan). No LLM needed. Effort: 3-4 days.

Activity

  1. added
    enhancementNew feature or request
    scope:code-intelCode intelligence — indexing, graph, impact analysis
    phase-3Phase 3: Architecture
    and removed
    phase-3Phase 3: Architecture
    on Aug 3, 2026
  2. ajianaz commented on Aug 3, 2026

    @ajianaz
    CollaboratorAuthor

    Implemented in PR #461 (merged to develop).

    What was delivered:

    • scan_breaking_changes() in engine/index_scanner.rs — detects breaking changes by cross-referencing removed/modified public symbols against callers
    • scan_dead_code_in_review() — dead code detection scoped to changed files (graceful no-op without index)
    • scan_unused_imports() — unused import detection (bonus)
    • Impact analysis in build_brain_context() / build_scan_context() — injects blast radius info into LLM prompt
    • MCP tools: cora.find_impact and cora.find_affected_tests exposed

    All deterministic findings — no LLM needed. IndexBridge pattern ensures graceful degradation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions