code_build

code_build compiles the project and returns errors mapped to named functions in the graph — not just file and line numbers. When the build fails, it automatically runs impact analysis on each broken function so you know what to fix first.

Usage

code_build()

Output (success)

Build passed — 0 errors, 3 warnings

Output (failure)

Build failed — 2 errors

error[E0308] in PaymentService.charge (src/services/payment.ts:42)
  expected `&str`, found `String`
  Dependents: 3 callers — CRITICAL: OrderService.checkout

error[E0432] in AuthService (src/middleware/auth.ts:8)
  unresolved import `jsonwebtoken`
  Dependents: 12 callers — CRITICAL: every authenticated route

Integrated impact analysis

When a build fails, code_build automatically shows the impact of each broken function. This tells you:

• Which errors to fix first (prioritize CRITICAL and HIGH dependents)
• What will break downstream until the error is resolved

When to use

• After every code change, before committing
• As the first step in the build-fix-verify loop
• Replace cargo build, npm run build, tsc — the graph mapping adds context those tools lack

Workflow

code_build()           → identify broken functions
code_get(name="...")   → read the broken function
# fix it
code_build()           → verify the fix compiled
code_test()            → confirm tests still pass