---
title: Repository Discovery
published: true
index: 20
---

# Repository Discovery

Use repository evidence when available and relevant to a Check; semantic search is optional. When Jevgrep (`jg`) is available, ask a behavior question scoped to the target/subtree:

```sh
command -v jg
jg "How does the cart update totals after a quantity change?" <target-repository>
```

Read returned excerpts and verify actual files/lines before deciding. Ranked paths are leads; relevance labels prove neither correctness nor coverage. Use `rg` for exact symbols, settings, types, filenames and follow-ups.

If Jevgrep fails, is incomplete or needs unavailable authentication, use direct reads and scoped `rg`. Do not install tools, request credentials or block a Check solely for missing semantic search. State actual source coverage.

Search locates evidence; it cannot assign outcomes, replace required browser evidence or narrow an authoritative catalog. Verify schemas and storefront behavior before recommending changes.