From brokk
Find symbol definitions by name regex, trace call sites with FQN, get symbol file locations, and explore class public APIs using Brokk's searchSymbols, scanUsages, getSymbolLocations, and getClassSkeletons tools.
npx claudepluginhub brokkai/brokk --plugin brokkThis skill uses the workspace's default tool permissions.
Use these Brokk MCP tools when you need to find where things are defined,
Semantic code search and navigation via the cix index. Use this when finding code by meaning rather than exact strings — cross-file lookups, symbol navigation, "where is X used", "how does Y work", "find authentication middleware", or exploring an unfamiliar codebase. Covers search, definitions, references, symbol search, file lookup, and indexing.
Guides use of Serena's LSP tools for symbol overviews, finding definitions, tracing references, and codebase exploration where grep is imprecise.
Locates production code definitions and usage sites (instantiations, calls, method invocations) for classes, functions, and methods. Use for 'where is X defined/called/instantiated?' queries.
Share bugs, ideas, or general feedback.
Use these Brokk MCP tools when you need to find where things are defined, who calls them, or how classes relate to each other.
| Tool | Purpose |
|---|---|
searchSymbols | Find class, method, or field definitions by name (regex) |
scanUsages | Find all call sites / references for a known symbol (needs FQN) |
getSymbolLocations | Get file + line for symbol definitions |
getClassSkeletons | Show a class's public API surface (fields + method signatures, no bodies) |
searchSymbols accepts a regex pattern -- use it when you know a name but
not the package.scanUsages requires a fully-qualified name (e.g. com.example.Foo.bar).
Use searchSymbols first if you only have a short name.getClassSkeletons is the fastest way to understand a class's API without
reading the full source.