codeindex-impact-analysis

Impact Analysis with CodeIndex

When to Use

• "Is it safe to change this function?"
• "What will break if I modify X?"
• "Show me the blast radius"
• "Who uses this code?"
• Before making non-trivial code changes
• Before committing — to understand what your changes affect

Workflow

1. codeindex_impact({target: "X", direction: "upstream"})  → What depends on this
2. READ codeindex://repo/{name}/processes                   → Check affected execution flows
3. codeindex_detect_changes()                               → Map current git changes to affected flows
4. Assess risk and report to user

In Conductor worktrees, "Index is stale" can be an overlay/canonical-checkout mismatch. Use scripts/codeindex-health.sh; only run scripts/codeindex-health.sh --repair when it reports the shared base index is stale. Verify branch-local code with source files/diffs.

Checklist

- [ ] codeindex_impact({target, direction: "upstream"}) to find dependents
- [ ] Review d=1 items first (these WILL BREAK)
- [ ] Check high-confidence (>0.8) dependencies
- [ ] READ processes to check affected execution flows
- [ ] codeindex_detect_changes() for pre-commit check
- [ ] Assess risk level and report to user

Understanding Output

Depth	Risk Level	Meaning
d=1	WILL BREAK	Direct callers/importers
d=2	LIKELY AFFECTED	Indirect dependencies
d=3	MAY NEED TESTING	Transitive effects

Risk Assessment

Affected	Risk
<5 symbols, few processes	LOW
5-15 symbols, 2-5 processes	MEDIUM
>15 symbols or many processes	HIGH
Critical path (auth, payments)	CRITICAL

Tools

codeindex_impact — the primary tool for symbol blast radius:

codeindex_impact({
  target: "validateUser",
  direction: "upstream",
  minConfidence: 0.8,
  maxDepth: 3
})

→ d=1 (WILL BREAK):
  - loginHandler (src/auth/login.ts:42) [CALLS, 100%]
  - apiMiddleware (src/api/middleware.ts:15) [CALLS, 100%]

→ d=2 (LIKELY AFFECTED):
  - authRouter (src/routes/auth.ts:22) [CALLS, 95%]