bronze · forge queryforge query

Sight across repos, not just one.

Forge is metalmind's cross-repo code graph. HTTP-route edges connect a caller in service A to its handler in service B - across language, framework, and repo boundaries - with provenance Claude can trust-grade.

01

Three edge tiers

OpenAPI specs on the metalmind shelf (never inside your repos), Java RestTemplate / WebClient / Feign callers, and URL string literals as an opt-in fallback. Each edge carries INFERRED_NAME, INFERRED_ROUTE, and INFERRED_URL_LITERAL provenance.

02

Reads your source directly

No indexing step and no external tool: forge walks each repo on demand and caches per repo, keyed on git state. Symbol-name edges connect a type or function declared in two different repos. symbolburn iron finds where a symbol is declared across every repo in the forge, and renameburn steel drives a coordinated rename through Serena's LSP backend.

03

Team-debug, primed

debugburn zinc hands a bug to the /team-debug skill. For inside a single repo, install codegraph alongside - it owns same-repo callers, callees, and blast radius.

§ Walkthrough

One query. Two repos. One answer.

A caller in billing-svc; a handler in notif-svc. Native Claude has no concept of "the other service's code." Forge does.

forge - graph query
# add each repo to the forge group, one per call
$ metalmind forge add payments ~/repos/billing-svc
$ metalmind forge add payments ~/repos/notif-svc
✓ 2 repos registered
 
# query across both
$ metalmind forge query payments "payment-failed"
 
→ billing-svc/src/handlers/charge.ts:142
notifyClient.post('/notifications/payment-failed', ...)
[INFERRED_ROUTE] openapi-shelf/notif-svc-v3.yaml
 
→ notif-svc/internal/handlers/payment.go:38
router.POST("/notifications/payment-failed", h.OnFail)
→ pushes to user_inbox + email_queue
 
claude: The flow is: charge.ts catches the failure → posts to notif-svc…
§ Trust grades

Every inferred edge carries provenance.

tier 1 - strongest
openapi specs

Pulled from your ~/.metalmind/specs/ shelf. Routes match exactly; types are checked.

tier 2 - medium
framework callers

Java RestTemplate, WebClient, Feign clients with annotated routes. Strong enough for navigation; verify before refactor.

tier 3 - opt-in
url literals

String-literal URL matching as a last resort. Off by default; surfaces with explicit INFERRED_URL_LITERAL grade.

Ready to give Claude eyes across every repo?

$ npm i -g metalmind ← Back to overview