Read the code that matters for a change
You need to change a handler in a large repository. Start with a narrow question: where is the handler defined, and which callers depend on it?
Locate the relevant matches
ashlr__grep accepts a pattern and a working directory (cwd). The registered tool describes genome-aware retrieval when an index exists and a ripgrep fallback otherwise. Start with a specific pattern and directory rather than a repository-wide search.
Treat compact reads as a starting point
ashlr__read preserves the head and tail of large files while eliding the middle. Its bypassSummary option skips model summarization but still returns snip-compacted content; it is not a full-file escape hatch. Use your host's native range reader when you need an omitted region before editing.
Sources: Registered read behavior and bypassSummary semantics
Check your own session ledger
The savings guide distinguishes benchmark results from session accounting and explains that small files may remain unchanged. Check the per-tool session breakdown rather than treating a benchmark percentage as a promise about the cost of your entire task.
Sources: Savings methodology and limitations
Try this workflow
- Install the plugin for your host using the installation guide below.
- Search within the relevant directory before opening entire files.
- Inspect matching files and surrounding control flow, using your host's native range reader for any elided region, then make and test the change.
Use ashlr__grep with cwd set to src/ to locate the request handler. Read the matching files with ashlr__read. If the relevant code is elided, use the host's native range reader before proposing an edit.Install and verify your host integration or open the quick install commands.