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.
How this skill is triggered — by the user, by Claude, or both
Slash command
/brokk:code-navigationThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use these Brokk MCP tools when you need to find where things are defined,
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.npx claudepluginhub brokkai/brokk --plugin brokkTraces symbol usages across a codebase, builds call hierarchies, and groups references by type (definition, import, usage). Requires grepika MCP server.
Reads code implementation details and file structures using Brokk tools: getClassSources for classes, getMethodSources for methods, getFileContents, skimFiles, and getFileSummaries. Use to explore code efficiently.
AST-aware code search, symbol navigation, and dependency graph analysis via the gcode CLI. Essential for exploring codebases, finding functions/classes, understanding call graphs, and checking blast radius before changes.