baz-codebase-exploration

Baz Codebase Exploration

This skill helps you plan a change across your org's repos using indexed search. It applies whether or not the relevant repos are checked out locally — and especially when a change crosses a contract boundary between repos: you edit one side, another repo defines the other. Baz MCP tools are how you search code across the org. Once you know a file's path, read it however you like — local Read if the repo is checked out, otherwise your own fetch.

When to use this skill

• The user asks to plan a feature, scope a change, or design an implementation
• The change might touch more than one repository in the org
• You own one side of a cross-repo contract (API param, request/response schema, event payload) — even when that side is checked out locally
• The relevant code lives in repos the user has not cloned locally

Tool routing — strict

Job	Tool
Find which repos are involved	repo_search (Baz)
Find code by symbol / regex inside a repo	remote_grep (Baz)
Find files by name / glob inside a repo	remote_file_search (Baz)

Forbidden — every kind of search goes through a Baz tool, never through your read or shell tool. These are the patterns that cause the most waste:

• Do not list or walk a repo's file tree to find files — no directory listing, no recursive tree fetch (e.g. gh api .../contents/<dir>, gh api .../git/trees/HEAD?recursive=1, ls/find over a checkout). Use remote_file_search.
• Do not crawl or scan a repo's contents to find a symbol or string (e.g. gh search code, grepping fetched files). Use remote_grep.
• Do not use your file-read mechanism (local Read, gh api .../contents/<path>, curl, …) for anything except opening one already-known file path. Pointing it at a directory, or firing several to "look around", is a search — route it through remote_file_search / remote_grep. The read tool is the last step, never the exploration.