Menu
Read implementation details and file structure using Brokk's get_symbol_sources, get_summaries, list_symbols, and get_file_contents tools.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Find symbol definitions, trace call sites, and discover related files using Brokk's search_symbols, get_symbol_locations, scan_usages, and most_relevant_files tools.
File discovery and code search using Brokk's search_symbols, search_file_contents, find_files_containing, and find_filenames tools.
Explore change history using Brokk's search_git_commit_messages, get_git_log, get_commit_diff, and analyze_git_hotspots tools, with Bash git/gh for blame and GitHub lookups.
Guided end-to-end issue resolution workflow: select a GitHub issue, diagnose the codebase, plan changes, implement in an isolated branch, review with specialist agents, and open a pull request.
Interactive guided code review: gather changes, run parallel specialist agents, then walk through findings one-by-one with code context, triage, and an overall summary.
Deep adversarial review of pull request changes covering security, code duplication, intent verification, infrastructure, and architecture using Brokk code intelligence tools and parallel specialist agents.
| name | brokk-code-reading |
| description | Read implementation details and file structure using Brokk's get_symbol_sources, get_summaries, list_symbols, and get_file_contents tools. |
Use these Brokk MCP tools to read source code at the right level of detail.
| Tool | Purpose |
|---|---|
get_symbol_sources | Full source blocks for one or more named symbols (classes, functions, fields) |
get_summaries | API surface for files, glob patterns, or class names (signatures + structure, no bodies) |
list_symbols | Compact recursive symbol outline for matching files |
get_file_contents | Raw text contents of one or more files |
get_symbol_ancestors | Ancestor class chain for known classes, when inheritance context matters |
get_summaries (or list_symbols for a more compact
output) when you need API shape, adjacent types, or package-level
structure before reading concrete bodies. get_summaries accepts glob
targets like src/auth/**/*.rs as well as class names.get_symbol_sources accepts an optional kind_filter (class,
function, field, module, any) to disambiguate when a short name
resolves in multiple kinds.get_symbol_sources when you only need a specific symbol's body --
it is much cheaper than reading the whole file. The kind_filter
replaces the old separate "method sources" vs. "class sources" tools.list_symbols when you need a quick declaration-level file outline
across a glob.get_file_contents; it takes project-relative or absolute paths
inside the active workspace.